Gregory Shaw wrote: > Another issue in the long term will be different operating system > revisions and nfs-mounted home directories. If the user installs > packages into their home directory for operating system revision X, when > the user logs into operating system revision Y, will it work? > > I think you'll have to keep the package information completely in > user-space for that to work. You'll also need a method to indicate the > target operating system revision and a method to segregate packages for > one OS revision from another. >
Well, we are keeping *all* user-based package info in user-space. There simply is no other place to put it. But as far as OS interoperability, this is more best practices fodder. This is similar to the advice that one would give to a user who wants to install Mozilla for x86, sparc, ppc, pa-risc, amd64, and all others, into $HOME. What do they do? > I'd envision a GUI tool at the user level that would keep track of their > own 'personal' packages that track updates, similar to update-manager. Yes, and we are working on that front as well (not as part of this project). For example, if 12 developers all install Java ES into their $HOME and register it with Sun Update Connection, then an OS admin who wants to install a critical patch to a component of Java ES can consult the Sun Update Connection system to figure out which of her systems have a domain with that component. > That would be very useful in the long term at a user level. Agreed. -jhf-
