Linked by David Adams on Thu 11th Dec 2008 00:15 UTC, submitted by Brian
Permalink for comment 340014
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2008-07-15
Well, it looks like others have covered most of the easy ways to do slack updates.
. Slack doesn't bother me with it, I like the fact that it assumes I know what I'm doing and just lets me do it. To be perfectly honest, I'm heartily sick of most of the package managers around today, and I'd prefer no automatic dependency resolution to getting my installation corrupted, thanks.
You're absolutely correct, no central repository and no dependency checking. And to that I say, thank goodness! I can't count the number of times I've wound up in dependency hell with deb or rpm-based distros due to an error in their central repository. It's probably just me and the packages I use, since it doesn't ever seem to happen to anyone else
And if you want dependency checking on slackware, as others have pointed out, you can have it. It's just not mandatory.