On 01/06/12 15:16, Albert White wrote:
Hi,
On 06/01/2012 20:58, Edward Pilatowicz wrote:
On Wed, Jan 04, 2012 at 03:27:26PM +0000, Peter Dennis wrote:
UPDATE SUMMARY
solaris
ips-incorporation
Installed 0.5.11,5.11-0.175.0.0.0.2.0
Possible 0.5.11,5.11-0.175.0.1.0.0.0
Possible 0.5.11,5.11-0.175.0.2.0.3.0 reboot required.
Possible 0.5.11,5.11-0.175.0.3.0.3.0 reboot required.
you can't determine if a reboot is required for a "possible" package
without actually creating a plan which installs that "possible" package.
True, but this is really a benefit for 'pkg update -n' which will go
through the plan creation phase and inform users if a reboot is needed.
If for some reason they want to update a group of packages but not
perform a reboot this would enable them to determine which packages can
be installed.
Realistically, any update at the moment provided for Solaris has all of
the components locked together in a standard supported configuration.
As a result, there isn't going to be anything a user can update
individually, so the point is largely moot.
The only place where this might be useful is for unbundled products such
as Cluster, Studio, etc.
Shawn, your proposal looks very useful. If it can use the
pkg.human-version that will make things even clearer for users.
Providing a 'human version' and the actual FMRI is fine provided that
the output does not become too verbose or confusing.
Yes, I was already planning on updating my proposal to use that. I had
that idea the same night I sent out the original one.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
