Linked by Thomas Leonard on Tue 16th Jan 2007 00:32 UTC
General Development In the Free and Open Source communities we are proud of our 'bazaar' model, where anyone can join in by setting up a project and publishing their programs. Users are free to pick and choose whatever software they want... provided they're happy to compile from source, resolve dependencies manually and give up automatic security and feature updates. In this essay, I introduce 'decentralised' installation systems, such as Autopackage and Zero Install, which aim to provide these missing features.
Thread beginning with comment 202069
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: yay!
by cerbie on Tue 16th Jan 2007 04:17 UTC in reply to "yay!"
Member since:

Hiding what it's doing means it's not installed? The files it saves its settings to don't count for installation, nor in some cases the virtual mounting thingie (yeah, I forgot the term)? It's nice packaging (I think still better than Klick), but is no more not installed than any other OS--the interface is just really simple, right down the file level.

For ports and things not available in such nice packages, it's generally more difficult. Of course the idea of using many directories off the root at the same time for a piece of software, rather than those being within it, is partly to blame (but it can save space).

IMO, since a Linux distro has finite software available in the repository, you should have all of it available through the GUIs, with some indicator that it is not installed, ten installing it upon first run. This would make things easy as a user, and still not annoyingly hide things if you want to do it some other way; or look inside.

Then, for third-party, just have scripts to support use of RPM and/or similar from the file managers (as in, you click, and it installs, and if the info is in there, even runs--I'm not sure of all the metadata in them).

Reply Parent Score: 2