Autopackage Struggling to Gain Acceptance
Linked by Eugenia Loli on Tue 13th Feb 2007 00:09 UTC, submitted by Dolores Parker
General Development 14 months ago, the Autopackage project was small and active, and members sounded optimistic about its success. Now, although the alternative installer project continues, progress has almost come to a halt. The #autopackage channel on irc.oftc.net sits vacant most days, the developer blogs cover almost anything except the project, and commits to the source code repository have become rare. Formally, the project is still alive, but the major contributors all agree that it is faltering. So what happened?
E-mail Print r 2   123 Comment(s) http://osne.ws/db0
Permalink for comment 212197
To read all comments associated with this story, please click here.
Siamhie
Member since:
2007-02-05

this is a big reason why you need a good package manager to resolve dependencies.

No you don't.

Slackware's package management is just as good as the ones found on any other distro.
The only difference is checking for dependencies is left up to the user.


http://www.slackbook.org/html/book.html#PACKAGE-MANAGEMENT

Apparently many people in the Linux community think that a packager manager must by definition include dependency checking. Well, that simply isn't the case, as Slackware most certainly does not. This is not to say that Slackware packages don't have dependencies, but rather that its package manager doesn't check for them. Dependency management is left up to the sysadmin, and that's the way we like it.

Reply Parent Score: 1