Shawn Walker wrote:
Some changes to the license action are needed to implement the
following RFEs:
5586 licenseinfo api needs to expose license action attributes
5732 packagemanager should have support for click-thru license
5943 'must_accept' attribute desired for license actions
This proposal is based on sch's proposal and the resulting discussions
[1].
========================================
Proposed Changes
========================================
* add a new boolean attribute named 'must_accept' to the license
action, which defaults to "false".
* add 'must_accept', 'license', and 'text' properties to the
pkg.client.api LicenseInfo object
* add a license-policy image property with possible values as follows:
-- accept - would accept any license with "must_accept=true"
Can we actually do this? It's great if we can.
[snip, this all seemed fine]
====================
Unresolved Issues
====================
* Implementing these changes would constitute a flag day for consumers
of the pkg(5) api and pkg(1). This might an undesirable impact on
projects such as the automated installer, etc. depending on which
packages had 'must_accept=True' set on their license actions. This
may require delaying the implementation of this functionality until
after 2009.06 (business requirements permitting).
+1 to delaying till after 2009.06.
* Retrieving the license information as I described above would incur
a hidden download time for users while licenses were retrieved from
the server (if not already downloaded). This means that a download
phase might have to be added just for plan evaluation (which is
eventually needed for manifest retrieval, so this seems moot).
Would it be possible to dispatch retrieving these licenses into
background threads rather than aggregating them all together? After plan
creation, it could wait for all those threads to finish, then proceed
(or proceed until a license it needs hasn't been delivered yet, then
stall on that thread, or just take each license as it's finished
downloading).
* Client memory usage for the plan creation phase would be increased
when the license-policy was "prompt" or "decline" depending upon the
number of licenses that have to be retrieved. In addition, the plan
creation phase time would also be lengthened due to the remote
retrieval of license information (if needed).
Are you planning on displaying the full text of the licenses (that seems
like a UI issue)? If not, I'm not sure how this is going to become
enough of a memory sink to be an issue.
Cheers,
Brock
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
