On Tue, May 27, 2008 at 11:14:11AM -0700, Danek Duvall wrote: > On Wed, May 21, 2008 at 11:07:56PM -0700, Joseph Di Pol wrote: > > > - developer B, already working on that system, gets menu items? > > But this is something you'd like to see? > [...] > > We've talked about having user images be "linked" to the full image they're > part of. I could see that linkage involving putting some system > integration bits outside the image, assuming full permissions. It almost > feels like relocatable vs absolute paths in SVr4 packages.
It might be nice if there was a way to specify mktemp'ed names if you did this (to avoid conflicts between multiple user image instances). But how does this work if you have an NFS/CIFS-mounted home directory? Note: networked homedirs complicate dependencies on non-user packages. One possible answer: this is for laptops, don't do that in enterprise environments. > Another thing to think about is that if the goal is to have a package > install into someone's home directory and install files in .gnome to do > gnome integration, the package will look quite different than if the goal > is to install it into a system directory, or a user image not associated > with a home directory (which is not a distinction we have at the moment, > but seems like it would be the norm for anyone doing multi-install). > Perhaps this is solved by tagging files appropriately, and filtering on > image type ... Also, it might be nice if we could get skel user images. Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
