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?
Yes that would be useful, particularly once we have the ability to
generate IPS packages out of ONNV builds and we are doing 'pkg
image-update' as the replacement for
'lucreate -n new ; bfu /path/to/ /.alt.new'
I'd want to be able to force a new BE some times so I can compare and
rollback.
> How about one to cause the operation
to fail if a new BE is required?
That depends on what the rules for BE creation are and what the defaults
are.
--
Darren J Moffat
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
