Tom Mueller (pkg-discuss) wrote: > The "updatetool" GUI used for SWI projects (Glassfish, etc.) already > does this. The code to fetch the licenses loops the the packageplans in > the imageplan, fetches the manifests, gets the license actions, and uses > the get_remote_opener on each license action to download the text. > > The client info command also fetches licenses, but it isn't part of the > install.
The API should certainly allow the retrieval of all information about the package, including licenses. That I can definitely agree with. What I meant was that, as far as I am aware, we weren't pursuing required, interactive prompting for installation as an option. > Shawn Walker wrote: >> Tom Mueller (pkg-discuss) wrote: >>> 2. One operation required by a GUI is the need to allow the user to >>> accept a license. How would that be done using this API? Would >>> action objects be exposed? The GUI must be able to download and get >>> the text of the license so that it can be shown to the user. >> >> I'm fairly certain that is not an option we are pursuing for the CLI, >> so it shouldn't be for the GUI either. >> > -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
