* Kyle McDonald <[email protected]> [2009-02-20 01:47]:
> Stephen Hahn wrote:
>>   The license action needs to support an attribute that requires the
>>   user to make an explicit acknowledgment to proceed with an
>>   installation.  I'm proposing we add a new attribute, must_accept, to
>>   the license action, such that clients must fail if an acceptance
>>   indicator is not provided by the user.  This indicator should end up
>>   in the image's operational history.
>>
>>   For the GUI, I would expect that the presence of the attribute would
>>   result in display of the license contents and a accept dialog.  I've
>>   noticed that NetBeans allows all licenses in a transaction to be
>>   accepted; one can also navigate license by license.
>>
>>   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.)
>
> What would unattended installation (like AI) do when it hit this type
> of action?  Or is this not an issue there?

  It is.  If you took a current AI setup, and changed a package to have
  a must_accept=true, then I would expect that package installation to
  fail, during evaluation.

  We'll have to add support for license acceptance to AI, either blanket
  or per-package (or both).  The workaround (other than "don't do that")
  would be to privately republish the package with a modified license.

  Thanks
  Stephen

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to