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? - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
