On 06/13/12 05:23, Mike Gerdts wrote:
[snip]
I don't see how pushing system software into a user image makes
sense. Perhaps my understanding of a user image is just way far off
from what others expect. I had expected that a user image would be
used for packaging software in a way that it didn't have to live in
the BE. In such a case, the only useful interaction between a system
image and a user image would be parent dependencies to say myappserver
(installed in a user image) requires openssl@mumble in the parent
image. Push the system openssl into the user image would not be
terribly useful unless it used and RPATH of $ORIGIN/../lib and had
similar mechanisms for finding configuration files, certs, etc. within
the user image.
I'm not so sure that there's benefit in reworking all of Solaris to
work nicely in the type of user image I've always envisioned. It
seems as though others view user images to be much more like system
images. Is that correct?
I don't think there's much agreement on what "user images" are. Some
people think they're images that live in a user's home dir that let them
install software and have the system image satisfy dependencies. Some
people think they're a way to install different versions of application
stacks on the same machine, even if they're not necessarily packaged in
a way that makes that easy. I would bet there are other interpretations
out there as well. Which interpretation is used, I think, directly
impacts whether or not the system image should enforce them staying in
sync. From my understanding of pull and push linked images, any image
that should be kept in sync with the GZ should be a push, while all
other image types should be pull.
Brock
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
