I have no problem

portpkg

or

source..

I use precompiled tgzs from pat or from slacky (dot) it. if I don't find anything else I search inside linux packages or for source (this is realy a boring think: I must compile, make a slackbuild to manage updates... build the tgz... uff...).
I'm also developing a script similar to slackpkg but with an "on the fly" dependency check for compiled stuff (I'm lazy and I don't like to make it by hand :P).

M

checkinstall, http://www.linuxpackages.net, kde's KPackage program. Before KPackage, I used slackpkg.

Slackpkg! First I tried swaret as in Shilo's guide, but that broke my install. Slackpkg rocks!
EDIT: Ironic twist: I just had to fix a problem. Some mirrors are broken.

I use swaret to update the standard packages to -current, and checkinstall on the source for others. I might investigate slackpkg or pkgbuild when I get a new HDD and install from scratch, but as long as I can use pkgtool to see everything that's installed and can uninstall easily from there, I'm happy.

I also use swaret for keeping up with current and use checkinstall for everything else.

I added 32 packages to my collection just this weekend, using PkgBuild. Actually, I'm testing a new wrapper front-end that makes most scripts unnecessary. You just call it like: 'src2pkg mytarball-0.1.tar.bz2' and it does the rest for an amazing number of packages. It accepts a few arguments also which help it succeed even more.

http://distro.ibiblio.org/pub/linux/.../ChangeLog.txt

Ironically, I've been severely compelled to upgrade to the latest version of -current. I usually don't worry so much about how -current my system is, but I do want to have a distinct plan... especially for when v11 arrives. I've been really thinking about just how to go about this and I've read some various literature about what a severe pain it can be upgrading the system. Apparently there are some things about doing a distro-upgrade that can really be a horror with slackware.

So I've been thinking heavily about having a working package manager like swaret or slackpkg simply for the distribution stuff that Pat compiles himself.. and everything else that's not there I can checkinstall or makeinstall myself. I seem to have ciotog and KMcd's vote...

I haven't had a plethora of time to dwell on it... but I'm going to take a look at gnashley's PkgBuild tool. Looks very interesting.

My current plan is to get a good system going as far as package/software management and then wipe this Hard Drive clean. Between Windows, Ubuntu, Fedora, and Slackware... I've screwed up a lot. Windows sucks and it's going. I broke Ubuntu then installed Fedora over its many partitions (/boot, /usr, /, etc.). Not to mention I have odd-sized partitions, unpartitioned space on the disk, the annoying windows garbage with the vfat partition that used to share data... and a Slackware distro that started as an experiement on a smaller, single partition.. which has been broken a few times in the interest of science and perfection. When slack 11 comes out this laptop is going to be fresh meat... and I would like to be able to keep it clean. I'm inheriting a 5-year old desktop fairly soon, and that will be my new linux toy.

So if you use the package managers to distro-upgrade... let me know what kind of problems (if any) that you ran into.

I'd also like to thank everyone for participating in my first poll! There are a few Slack noobs that were able to get something from it I'm sure.

Yeah..as author of Stratdate, I am a little alarmed at the fact that my software has been lumped in together with all of the other dependency tracking managers. Stratdate does NOT track and handle dependencies. All it does is rsync with a -current mirror, and allow you to bring your machine to -current the official way that Pat says that all version upgrades should be done (Runlevel 1, yadda yadda yadda).

[Off-Topic]

@ gnashley,

Hey Gilbert, I was wondering about the current status of your Amigo project.......It seems the ibibilio site no longer has all that it used to a year ago.......I'm interested in the Pkgbuild tools and would like to know if it's still being maintained, or have you abandoned it altogether?.......

I was starting a bash-based build program a while back when I first came across the Amigo project, and I was quite interested in it..........I don't like to reinvent the wheel much, so I moved on to other things at the time....

PM me if you like so as not to pollute this thread any more than it already is....... ;-)

[/Off-Topic]

Slackpkg for the tree, SlackBuilds for everything else.

It depends on the package I want. Sometimes I'll pull packages down from Source Forge and compile my own. I'll sometimes use Patrick's packages and also the packages at SlackBuilds.org.
It is great to have so many choices.

I install most things from source (if not, then from Alien Bob or Slackbuilds.org), and I use paco for source package management.

@the geekster :
http://www.linuxquestions.org/questi...d.php?t=560844

-----
ontopic: http://klik.atekon.de/ is interesting.

slapt-get for official packages.

makepkg/installpkg/upgradepkg for everything else.