Bart Smaalders wrote:
I'm looking at making pkg install and pkg image-update do the
right thing wrt boot environments. We're already tagging files that
should require a reboot if modified in the live system w/
the reboot_needed tag. What I'm considering doing is making
pkg install and pkg image-update use this as the deciding
factor as to whether or not to create a new boot environment.
This way, a security update that only has a new version of
firefox won't create a new BE during image-update, but
pkg install ent...@116 would.
Do people want an option to force both pkg install and pkg image-update
to always create a new BE? How about one to cause the operation
to fail if a new BE is required?
I think both are reasonable, but one twist I'm not clear we've
considered: should we be tagging SMF service binaries in order to ensure
they get restarted in the live image (as distinct from tagging the
manifests with the manifest-import FMRI)? I think there's a consistency
of user experience argument that says we should do so, otherwise you end
up with the package incompletely applied, in terms of what's actually
running.
Dave
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
