Tom Mueller wrote: > Brock Pytlik wrote: >> Could you explain what you mean by change list? >> > In the presentation that Stephen did at the OpenSolaris meeting back > in June, he talked about moving the data from the patch README file > into package attributes. This is where one would find the list of bugs > that are fixed in that version and that sort of information. To > present a complete picture of what has changed between the current > version and a version to be installed, the client would need to gather > the information from all intermediate versions (presumably using search). Ah. Now I understand. I agree, the API needs to provide some mechanism for getting this information eventually. What that mechanism will be, I don't know. Unless the GUI plans on adding this feature, I'll put off designing this until probably stage 3 of the API.
For general reference b/c I don't think I've said this here, I'm envisioning 3 stages of API development. Stage 1 (where we are now): Fix critical paths, like install, uninstall, and image update. Introduce new API methods to prevent new code duplication. Stage 2: Introduce API methods for all modifying actions a user could take: set-authority, image-create, etc... Stage 3: Introduce API methods for all other actions: list, search, contents, etc... Brock > > Tom > > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
