On 8/20/12 11:06 PM, Shawn Walker wrote:
On 08/20/12 16:40, Liane Praza wrote:
On 08/19/12 23:50, Shawn Walker wrote:
Greetings,
The following draft webrev and sample output is for the following
bugfix/RFE:
7134154 install/image-update/uninstall -n uninformative
Sample output:
https://cr.opensolaris.org/action/browse/pkg/swalker/pkg-7134154-1/pcs_samples.txt
I just took a quick glance through, so my comments might not be
comprehensive.
- Will this use a "human-friendly" attribute if set? Can we see the
proposed output for that, if so?
Yes, I just didn't have any packages when I was doing the run-through that had
one.
Yeah, should definitely open the RE bug so that this gets populated on
entire. (And probably a bug per consolidation so that interim builds get
marked for consolidations' incorporations as well, when possible.) I'll
try to follow up on that separately (or: Oy! Alan! Sound like a good
idea?). But if you could open the RE one, that'd be helpful.
Here are two samples (best viewed with a monospace font):
# Update from b20 to b22.1; note the pkg.human-version I set was
# arbitrary. It could just as well have been 'Solaris 11 Update 1'.
# The below is a success case:
$ pkg update -n
Packages to update: 13
Create boot environment: No
Create backup boot environment: No
Package Change Summary
Package: entire
Installed: 0.5.11-0.175.1.0.0.20.0
Proposed (Latest): Update 1 Build 22.1
$
# Here's an "error" case -- that is, either a case where we found no
# solution or there were no updates available:
$ pkg update --no-refresh -n entire
Package Status Summary
Package: entire
Installed (Frozen): 0.5.11-0.175.1.0.0.20.0
Latest: Update 1 Build 22.1 (0.5.11-0.175.1.0.0.22.1)
No updates available for this image.
$
# Note that in an "unsuccessful" operation case, the actual version
# is shown in parentheses next to the pkg.human-version as show above.
I think it's obvious what it would look like if both had a pkg.human-version.
That's awesome. Thanks!
- I'm vaguely wondering if it's useful to print the Installed version if
there are updates to do. Like in the last example, maybe it should just
say the proposed lines. If there are no updates, Installed is always
useful.
But, I'm happy to hear others' take on that. Could argue it either way.
I think I mostly don't need the "what I have" info if I'm updating
somewhere, and I can obviously always get it with pkg list/info.
I could see that; I suppose the argument could be made that in a success
scenario, the user likely knows what bits they already have and where they're
going to and could go is the interesting part. That's trivial to do, I'd like
to hear what others have to think as well.
I too am curious as to what others think.
OK, will let this percolate, then.
- Frozen error messages are a real bummer... Not your doing, but I'm a bit
surprised the solver doesn't diagnose when something's frozen and
explicitly give that as cause rather than dumping the "no solutions to
satisfy constraints" message.
Generally, though, this is a real improvement in optics about what an
update did. Thanks for tackling phase 1.
Thanks. There's a lot more that could be done here, but this is as much as
I'm willing to take on right now. I have opened/commented on several
RFEs/bugs recently related to the solver messaging.
liane
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
