On 01/12/12 04:28 PM, Shawn Walker wrote:
END-USER EXAMPLES ================= These examples assume 'entire' is installed and nothing has been version-unlocked: # pkg update -n ... PACKAGE CHANGE SUMMARY solaris entire Installed: FCS Build 2 (0.5.11-0.175.0.0.0.2.0) Proposed: SRU 2 Build 3 (0.5.11-0.175.0.2.0.3.0) ... Shows an update from S11 release to the latest SRU. 'entire' is shown because it is the top-level of the install-hold chain (in this case, 'core-os'). The other incorporations are hidden even though they are changing because they are incorporated by the package delivering the 'core-os' install hold.
Bonus points if you can work a release-notes-url attribute in there as well, so you can show it before upgrade if desired, and not have to have each branch of pkg hardcode the release notes URL for that branch/release in the pkg code. So the above could then become: ... PACKAGE CHANGE SUMMARY solaris entire Installed: FCS Build 2 (0.5.11-0.175.0.0.0.2.0) Proposed: SRU 2 Build 3 (0.5.11-0.175.0.2.0.3.0) Release Notes: http://support.oracle.com/..../s11-sru2.html ... And at the end of an actual update: NOTE: Please review release notes for this update at: Oracle Solaris 11 SRU 2 Build 3 http://support.oracle.com/..../s11-sru2.html Oracle Solaris Studio 12.3 SRU 1 Build 4 http://support.oracle.com/..../studio12.3-sru1.html for any incorporation in which there's a new release note attribute installed by the updates you just completed. Not that your work isn't already a huge step forward, this would just be icing on the cake. -- -Alan Coopersmith- [email protected] Oracle Solaris Engineering - http://blogs.oracle.com/alanc _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
