On Tue, Dec 15, 2009 at 07:46:27PM -0600, Shawn Walker wrote: > The issue is that the client needs access to all of the license > information after plan creation (evaluation) and *before* plan > execution (when actual package files are downloaded).
<...> > So I'm not sure how to balance simplifying the retrieval of the > licenses while avoiding license retrieval unless necessary. I have an idea, but I'm not sure if it meets all of the requirements for this feature. Is it feasible to change the point in time when the licenses are displayed? The code in the gate always requires us to download a license. If it were okay to display the license after the content has been downloaded, but before it is installed, then you could perform the download in one step. Afterwards, the client could then display the license information. This doesn't get you out of having to deal with compressed license files, but it does mean that the download doesn't have to happen in two phases. If the user opts not to accept the license, we can still skip installing the packages. Is this a workable idea? > Ideally, the client should be able to get at all of the license > information separately from all of the rest. In other words, > something like "image-update -n --licenses" should give them the > license information for all updated packages. I'm less certain about the best way to handle this scenario, but if you look at remote_search() in api.py, that's a good example of what execeptions you'll need to catch if you're using get_datastream(). -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
