On Thu 19 Feb 2009 at 05:43PM, Stephen Hahn wrote:
> For the CLI, I propose that the operation fail unless a
> --accept-license option is presented. Failure should present the list
> of licenses requiring acceptance, and their associated package. (The
> --license option to pkg info allows license text review.)
Stephen-- thanks for typing this up.
Having to type --accept-license seems like a pain (and yes, I know
that licenses in general are a pain), and it seems like I would now have
to universally replace every invocation of pkg(1) in my scripts with
'pkg --accept-license'. And what should we do about places where
pkg(1) is nested inside of something else-- as with the zone
installation?
I know we want to avoid interactivity, but could we somehow make this
smoother? Could the license policy be an image level configation
knob?
IOW:
pkg set-property licence-policy decline-when-required (the default)
pkg set-property licence-policy accept-when-required
pkg set-property licence-policy prompt-when-required (could also be the
default)
This could pair up with an option which allows override of whatever
the image's default is.
pkg --license-policy=decline
pkg --license-policy=accept
pkg --license-policy=prompt
I'm oblivious to the constraints on this problem which might have
been expressed by legal, marketing, etc.
I'm just mostly concerned that this could create a "ticking time
bomb" of a failure mode-- an admin's scripts will all work fine, until
they don't. Another possibility would be a unique exit code for
licensing acceptance failures, I guess.
-dp
--
Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
