Linked by David Adams on Thu 11th Dec 2008 00:15 UTC, submitted by Brian
Thread beginning with comment 339995
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.
RE[3]: Embarrassing question, but I'd like to know...
by setec_astronomy on Thu 11th Dec 2008 16:26
in reply to "RE[2]: Embarrassing question, but I'd like to know..."
Thanks for adding this information, I meant to lookup slackpck when I wrote my comment but somehow mixed it up with slapt-get in my memory (talking about embarrasing things, ... )
As I mentioned earlier, my knowledge about additional packaging systems is rather limited, since I have not used anything besides pkgtools + slackbuilds.org in the past five years or so and my scripts for handling the updates in a semi-automatic way are pretty much unchanged since 10.0 .
I would still recommend subscribing to the security advisory list, though.
RE[3]: Embarrassing question, but I'd like to know...
by justinc on Thu 11th Dec 2008 19:22
in reply to "RE[2]: Embarrassing question, but I'd like to know..."






Member since:
2005-06-29
No, a much better way of managing updates is to use slackpkg which was in /extra for a long time and now is included as part of the base Slackware installation. Slackpkg will let you install extra software from the official Slackware mirrors, including updates in the /patches directory.
For third party software, I encourage you to check out the site mentioned in Patrick's announcement: slackbuilds.org. This site is run by several members of the Slackware team and provides a repository of slackbuild scripts that are vetted by the admins for tons of third party software. You can also use a tool called 'sbopkg' (www.sbopkg.org) that provides a nice dialog-based front-end to slackbuilds.org. Slackbuilds are simply shell scripts that are used to compile third-party software into Slackware packages. As a long time Slackware user, I do not use unknown binary packages from places like linuxpackages.net (those packages often break people's systems) or outside tools like slapt-get etc. that are poorly bolted on to the official Slackware package manager and package tools.
Slackware + slackpkg + slackbuilds.org + sbopkg is all you need. ;-)
Edited 2008-12-11 16:09 UTC