Linked by Eugenia Loli-Queru on Tue 13th Feb 2007 00:09 UTC, submitted by Dolores Parker
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?
Thread beginning with comment 212162
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[2]: Autopackage is a good idea...
by Siamhie on Tue 13th Feb 2007 08:42
in reply to "RE: Autopackage is a good idea..."
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.
RE[3]: Autopackage is a good idea...
by superstoned on Tue 13th Feb 2007 10:05
in reply to "RE[2]: Autopackage is a good idea..."
Member since:2005-07-07
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-23
godsolete: What's this SLL hell you're on about?
Just about everything on my Linux box at home is dynamically linked - this is a big reason why you need a good package manager to resolve dependencies.
Personally, I feel like Autopackage didn't gain any traction because it's a solution in search of a problem. There already are plenty of good package managers and frontends. If people have trouble using them, it's not because Ubuntu provides a bad frontend to it, it's because they want it to be just like Windows. Autopackage didn't address that, which IMO is about the only real (albeit large) obstacle package managers face.