Brock Pytlik wrote:
Shawn Walker wrote:
* 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.
As far as I know.
* 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).
Not at the moment; our APIs aren't really thread safe and the new
transport layer will initially not support this either.
* 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.
The full text of the licenses has to be retrieved so that the client can
choose how to display them.
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
