Linked by Tom5 on Tue 24th May 2011 21:13 UTC
Thread beginning with comment 474558
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.
I remember when we first got 0install into the Debian repository, I had to spend quite a long time convincing them that it wasn't like Autopackage!
I think the main issue was this: if an Autopackage needed a newer version of a library than the one Debian had installed, it would move Debian's copy out of the way and replace it with its own. So there was a risk that other programs on the system would stop working, and Debian would get confusing bug reports.
0install never does that: a library added by 0install is only visible to other 0install programs (and, in fact, only to those which depend on it explicitly).




Member since:
2010-05-17
I covered Autopackage years ago in Tux Magazine and it seemed to have more potential to me than others, including 0install. One of the major barriers seemed to be Debian people, who went all religious on their 'ass', and even banned Autopackage developers from their IRC channels. That sort of thing was really demoralising, and despite the fact it had interest from parties like IBM, idiotic zealots from other projects killed it.
Sometimes we're our own worst enemies.
I wasn't nearly as much a fan of 0install last time I tried it (although I imagine it's much improved over the years) as the very familiar and intuitive interface as Autopackage, but heck, good luck to 'em.