On 02/12/10 11:59 AM, Nicolas Williams wrote:
On Fri, Feb 12, 2010 at 11:38:17AM -0600, Shawn Walker wrote:
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 '/'.
Far simpler: require an explicit option in order to operate on images
other than /. Make / the default image.
Yes, that's an admin-centric point of view.
I don't see the issue in allowing a user explicit control over the
behaviour via an 'rc' file. Please elaborate on why users should be
forced to type -R over and over again if their primary usage pattern is
centered around something other than '/'.
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.
Users who know enough about user images and the CLI can be expected to
use an explicit option (because they can be expected to RTFM). All
other users will never have any surprises (since either they will be
using the GUI, which could make the choice of image explicit and
inescapable, or else they won't manage user images at all).
I disagree; we need a reasonable compromise here that can accommodate
both privileged and unprivileged users.
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
