On 11/10/10 06:11 PM, Rich Burridge wrote:
On 11/10/2010 03:03 PM, Dave Miner wrote:
On 11/10/10 05:34 PM, Danek Duvall wrote:
Shawn Walker wrote:
And yes, I'm aware they're separate now so that --require-new-be
doesn't force you to provide the BE name. However, I wonder how
much value there is in that.
If you don't care about your BE names, and are happy with solaris-N,
then
you don't use --be-name. I think people who do that are mental. :)
The thing you can do is, just once, use --be-name to set it to
"snv-<buildnum>" and then let auto-increment handle it from there and
your BE's match builds.
Except when you upgrade from (say) build #151 to #151.0.1.
The new BE would then be called snv-152.
I solved that by going on vacation and just missing 151 entirely :-)
Dave
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
