On 2/17/2012 8:47 PM, Jason J. W. Williams wrote: > This is a huge issue for Chef and Puppet. The reason is that when pkg > creates a new BE for a package, Chef/Puppet make the configuration > file changes in the currently live BE. When you reboot, you end up > with an inconsistent environment missing all of the changes Chef > deployed simply because pkg decided a new BE was required. So far > I've just been culling those package from Chef's control that cause > the issue, but GCC is not one I can do that with.
Rather than hacking around the problem by eliminating the useful BE creation process, why not fix the broken Chef/Puppet behavior? Modifying the current configuration makes no sense here. -- James Carlson 42.703N 71.076W <carls...@workingcode.com> _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
