Bart Smaalders wrote:
Following up on a thread from several months ago....
Currently, the pkg command deals rather simplistically with boot
environments; it always creates a new boot environent when doing an
image update or change-variant, and never does one on pkg install. We
recently enhanced pkg install and uninstall to prevent operation on
the live image if doing so would modify files tagged with
reboot-needed=true. However, it would be nice if pkg(1) could be a
little more malleable.
We can add the following option to install, uninstall, image-update
and change-variant and change-facet:
--new-be=[always, if-needed, never]
So it was pointed out to me off-list that there are a few other things
we may want to consider:
* exposure of the boot env options on platforms where they don't apply
(not a primary concern for our project; primarily experience/cosmetic in
nature since the bootenv module makes this a no-op on other platforms)
* possible confusion w/ user-images? (and what to do about snapshots...)
This also occurred to me as well:
* repeated package operations in the packagemanager GUI or with the cli
after a be creation has occurred; specifically, it seems like we need a
mechanism to warn the user about (but not prevent) subsequent operations
until they've restarted the system (at the least?)
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
