This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new Linux.com!

Linux.com

Re:The problem with zero-install

Posted by: Anonymous Coward on February 16, 2007 08:40 PM
The main problem with zero-install is that it's over decentralised. If your program depends on gtk it will get it from www.gtk.org.

By default, yes. You (the user) can specify somewhere else, though if you want (double-click on GTK, then click on 'Add Remote Feed' and type in its URL).

Note that the packages don't normally contain the URIs of the libraries they use. Instead, the XML description of the package gives the dependencies. So, if in 2017 the gtk.org stuff has moved to <a href="http://archive.org/2007" title="archive.org">http://archive.org/2007</a archive.org> then the author of the program using GTK would just edit the XML to give the new location (or someone else could publish the updated XML, if the original author had disappeared).

This dose mean that zero-install programs share
dependencies but its not so good if you want to install something in 10 years time.


Well, this is covered by support for mirrors. As long as someone kept a copy of GTK you can use that. Presumably whoever archived the 10 year old program would have archived its dependencies too.

Really what is needed is some way of createing a<nobr> <wbr></nobr>.tar.gz that includes all dependencies

Like this?

<a href="http://rox.sourceforge.net/desktop/Zero2Bundle" title="sourceforge.net">http://rox.sourceforge.net/desktop/Zero2Bundle</a sourceforge.net>

#

Return to Zero Install: An executable critique of native package systems