On 09/21/10 11:11 AM, Glenn Lagasse wrote:
* Danek Duvall ([email protected]) wrote:
Nirmal Agarwal wrote:
Sorry for not being too explicit in the previous mail. I wanted to
understand the use of "--be-name" with "pkg install" command (and
not with pkg image-update.).
It's exactly the same. Try to forget, if you can, the fact that
image-update used to always create a new boot environment, and install
never did. Now, both will do so if necessary, and only if necessary. That
necessity is determined by whether any actions tagged with reboot-needed
are being updated and the operation is being done on the live root.
Thus, if image-update would only bring you a new version of the compilers
and openoffice, it won't bother with a new BE, but if you say "pkg install
ent...@new-build", then you'll get a new boot environment. You kinda have
to know in advance whether a new boot environment will be created to know
whether the --be-name option will be useful.
[sorry I'm late to this discussion, I was on vacation]
That seems pretty unuseful and not very user friendly to have to know
before hand whether or not one needs the --be-name option for pkg
install. Are there any plans to make this more usable to an end-user so
that they don't have to be the equivalent of a mind-reader?
If you run an install or image-update operation with '-n' on build 147
or later, it will tell you if the operation will create a new BE.
Beyond that, I'm uncertain what else could be done here as the pkg(1)
command is not interactive (intentionally).
But as Danek noted, you don't *need* the option; it's there as a matter
of convenience.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
