On 02/11/10 17:06, Brock Pytlik wrote:
I think that's a false analogy. The effect would be have their action happen on a more limited basis, not a larger one. So instead of installing the package into the root system, they'll install into their user image. Also, if a sysadmin didn't like this behavior, they could remove their user image, or set their PKG_IMAGE to default to /. This places the burden on the admin to account for their image correctly instead of placing that load on every user.
If the burden could be as simple as specifying a one-character search-for-local-image flag to pkg, I think you might be overestimating the costs -- especially considering you're weighing a known use case against a hypothetical future one.
As a side note, notice I suggested that the check should actually to be to check user's home dir if PKG_IMAGE wasn't set, not the current dir. I mentioned cd'ing to / only if there was a reason that we didn't want to go with the other method.
Checking only their home directory would indeed be safer. I was under the impression that per-homedir images were merely an example of non-system images, though, not the primary consumer. A hard-coded home directory test serves a pretty narrow audience. Dave _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
