On 02/11/10 06:21 PM, Nicolas Williams wrote:
On Fri, Feb 12, 2010 at 10:10:27AM +1000, James C. McPherson wrote:
Perhaps this should be is user's homedir a user/partial image?
Brock
/
2) Is / a full image
3) Is there a full image higher than / that I'm sitting in
Hang on a sec - why would a user have an image or partial
image setup in their homedir? Why should that be the first
check that you make?
Surely we should be assuming that anybody running "pkg image-update"
is not wanting to update a system, and instead wants to update
a home directory?
+1
I've yet to figure out how to make user images work, and I suspect that
they don't really. But even if they did work perfectly, I'd still
think, like you, that operating on a user image should require that the
user explicitly request that. The default should be that pkg(1)
operates on the booted BE's image -- anything else is deeply counter-
intuitive.
User images work (afaik) as expected as long as they only express
self-contained dependencies. That is, as long as they want to install
packages that can be installed into an arbitrary root, have correct
runpaths, etc.
As you're probably aware, the Glassfish team has used pkg(5) to
distribute their product for quite a while now, and user images are what
they use. (See the UpdateCenter2 tool.)
With that said, the last bit (afaik) of functionality that has not yet
been implemented for user images is the ability for them to have a
parent image that can be used for non-relocatable dependencies, etc. so
that you can install one-off packages inside the user image while using
the dependencies in the parent.
Finally, I'm also not convinced that the current automatic directory
path search is the best idea either. As such, I'd like to suggest the
following:
The process would be, *if* -R or PKG_IMAGE wasn't already set:
* check for a ~/.pkg5rc or /etc/pkg5rc
* pkg5rc does not exist; assume '/'.
* pkg5rc exists, open that, and get paths for images
-- If any paths were listed, then whatever path is most specific to
the current CWD is the image pkg(1) would use, otherwise it would
fallback to '/'.
That would allow users to easily control the behaviour (with little or
no surprises) in combination with the existing -R / and PKG_IMAGE
environment variable.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
