On 01/04/12 14:10, Chris Quenelle wrote:
On Wednesday January 4, at 11:40AM, Shawn Walker wrote:
On 01/04/12 11:24, Chris Quenelle wrote:
Can you change "solaris" to "publisher: solaris" ?
And maybe a label for the package as well?
I've been purposely avoiding labels for those items because of the extra noise
it creates in the output. I might be convinced that the publisher one needs
it, but I have mixed feelings about the package one.
Is there anything else I need to do to convince you to add "publisher:" ? :-)
I'm willing to drop my request for a package "kind" as long as the full
path is always printed. I was worried about the typo that you acknowledged
below.
...
While all the version components are single digits, the lines
are all nicely lined up. It would be easier to evaluate the long-term
legibility if you would use some two digit numbers in your examples.
Left-justification within the field will be guaranteed for the versions, so
yes, there could be a jagged edge on the right side if version lengths are
variable.
I'm not concerned about the jagged right edge, I'm concerned about how hard it
is to
see which digit constitutes an SRU update and which ones are for respins, etc.
The 6-part version numbers are going to be gobbledy goop to anyone
outside the Oracle Systems org.
It might be a nice RFE to be able to load a schema into an IPS repo that
would simply allocate field names to version components. The the pkg
command could use those field names in certain output formats.
Probably the schema could be assigned on a repo-wide basis?
It seems like a tangent, but it's related to readability, so that's
why I bring it up.
I don't think that's practical. The only packages that are likely to
have the same versioning scheme are those published for Solaris, and
even then, there's not a strict guarantee of that, especially the
farther back you go in pkg history.
However, I think I have a better solution that I was already considering
before you mentioned this. I'll send out an updated version of this
proposal soon that incorporates feedback so far along with that.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
