On Fri, 2006-06-02 at 22:11, Vasiliy wrote: > It should be clearly stated what is it for, because there are two different > use scenario I see here:
Indeed, although I would look at the two scenarios somewhat differently: 1. Personal user software (apps, plugins, ...). 2. Delegated software administration (JES, databases, ...). Now my reading of the original proposal was largely biased towards the first, and I still don't think packages are necessarily appropriate in that case. Some of the things (especially what Dave's been trying to get through my thick skull) make much more sense within the context of the second scenario. The scope of the problem can be restricted to a single system. The type of applications that might fall into this category may well provide services and should be properly managed. (And may well be deployed in environments where the provision of a network-wide registry may be possible.) Is this second scenario user-based install though? Chances are that root access may stil be required - creating filesystems (could be delegated with zfs, I guess); installing startup scripts. -- -Peter Tribble L.I.S., University of Hertfordshire - http://www.herts.ac.uk/ http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
