* Tom Mueller (pkg-discuss) <[EMAIL PROTECTED]> [2008-05-21 14:20]:
> With GNOME and a non-root user, doesn't the file have to be installed
> under $HOME/.gnome somewhere? This directory is typically not going to be
> within the user image so a simple install of a file doesn't work. Also,
> if the same application is installed three times in different user images
> by a user (slightly different versions), there needs to be some resolution
> regarding multiple menu entries. On Windows its a whole different story
> with registry editing, etc.
This expansion starts to suggest why this use case is confused.
It leads me to the question of when does an installation into a user
image affect a particular resource outside that image? The safe
answer is never, so what exceptions do we feel have to be made? One
aspect of the menu items that bothers me is from the enterprise
developer scenario:
- tools master A creates user image with stack 1.0
- tools master A gets menu items?
- developer B, already working on that system, gets menu items?
- developer C joins company, is told to use stack 1.0 provided by
tools master A
- developer C gets menu items how?
I'm pretty sure that developer C's menu items need to be installed by
a mechanism *other* than packaging. I suspect that's true for
developer B, too. It gets even truer when we start to think about
removal...
Do we have a different example from menu items?
(As an aside, one intended aspect of user images *is* to allow a
user's home directory to be a user image. That makes delivery into
$HOME/.foo straightforward.)
- Stephen
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
