Hi Everyone.
After reading this:
My first question does slackware 12 include 12.1?

Secondly, what are you using for controlled source install? I have been reading about src2pkg on here but have never used it.

If you are not able to write a SlackBuild script for the application you need, you'd better see if the application is not available in www.slackbuilds.org or in www.slacky.eu. If it is not there you should use src2pkg - it is a tool that excels checkinstall.

Src2pkg all the way baby. Fine, fine piece of software.

You should learn how to use SlackBuild scripts. The official Slackware packages are (almost) all built in a controlled fashion, using scripts that are called SlackBuilds, after the extension all these scripts have.
The SlackBuilds.org web site is an example of a repository of unofficial SlackBuild scripts and has a HOWTO section about how to create packages using SlackBuild scripts. Anything built and installed as a package, can be upgraded or removed from your computer in a relatively easy way.
Several repositories exist of pre-compiled Slackware packages that also come with the SlackBuild scripts that were used to build them. Slacky.eu was already mentioned; Robby Workman has a lot, I have a lot as well.
You should look at the Slackware Links page at LQ - http://wiki.linuxquestions.org/wiki/Slackware-Links .. it has a lot of useful information.

Eric

Other - I compile my own packages.

Pat V. uses SlackBuilds. Every package in Slackware was compiled using one.
I normally use SlackBuilds from slackbuilds.org, rworkman, Alien Bob, or one of
Pat's. (As a last resort, I'll write my own.)

It just seems like the preferred method of getting a Slackware .tgz package.

Don't see it as a choice in the poll though. Had to vote "other".

Edit:
If you're interested, Chess Griffin has written a nifty little tool
especially for the slackbuilds.org site.
http://code.google.com/p/sbopkg/

I think the question was about 'alternatives to checkinstall' rather than 'what is the best way to obtain and build packages'. That is why I voted for src2pkg. Otherwise I would have said SlackBuilds also.

Same here. Years ago, I would use checkinstall or binary packages from various places. Now, I only use SlackBuilds.

Hi Alien Bob I will definitly check that out. I havent used slackware since 10 and do remember using some scripts to build/compile packages but nothing as complete as what there is at slackbuilds.org.

I am going to give it a go Now if only I could find the source code for picasa.

**Thanks for all your input its very interesting!

Other - Custom SlackBuilds since i like to keep my /tmp clean

I use paco, but I've used the others and they're good too.

C-Sniper, src2pkg makes it easy to build packages without using /tmp. I personally build everything in the current directory which makes it easier to inspect both the source and package content.

Src2pkg mainly, but sometimes use a slackbuild.

Thanks Gnashley, i understand this as i used Src2pkg before i learned how to write SlackBuilds. But the latter gives me something to do at the office

I prefer to put things in /opt/<packagename-version> and then use symlinks or wrapper scripts in a directory in the $PATH. Removing them is then a case of a simple 'rm -rf' and cleaning up any broken symlinks. This has the advantage that you can have multiple versions installed concurrently as long as you manage the symlinks appropriately.

Alternatively, if the software isn't suitably standalone for this sort of approach I normally knock up a quick slackbuild/package and stick it under /usr with everything else, but I prefer /opt wherever practical.

/usr/local I keep for the programs/scripts I've written myself.