Linked by Thom Holwerda on Fri 15th Jun 2007 22:13 UTC, submitted by lost
Thread beginning with comment 248333
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2007-01-27
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.