Linked by Thom Holwerda on Fri 15th Jun 2007 22:13 UTC, submitted by lost
Slackware, Slax Patrick J. Volkerding announced the first release candidate of Slackware 12 in the current changelog. This will be the first Slackware release with a kernel from the 2.6 tree ( as default. "It's that time again, and here we have Slackware 12.0 release candidate 1! If we're lucky, we got it all right the first time. Big thanks to the crew."
Thread beginning with comment 248333
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: package manager
by psychicist on Sat 16th Jun 2007 08:34 UTC in reply to "package manager"
Member since:

Of course it does! Slackware packages are just tar(-1.13) files compressed with gzip. Whereas RPM obscures the creation of packages through the lack of transparent build scripts, Slackware just uses shell scripts to create packages.

Slackware has pkgtools to manage packages. There is no inherent dependency resolution, which could be seen as both a good and a bad thing. In this respect it adheres very much to the Unix philosophy to keep it simple.

In contrast with RPM and DEB which do dependency resolution in the basic package managers themselves (rpm and dpkg) the basic pkgtools only supply mechanism and no policy.

So you can install, remove and upgrade any package you want without the tools keeping you from hosing the system. This is really the best way to do it, especially for experienced users that don't want to fight the package manager.

The dependency resolution is left to third party tools such as slapt-get, slackpkg and others, which do a lot but not all of what RPM tools such as yum and DEB tools such as apt-get are supposed to do.

Reply Parent Score: 5