On Mon, Apr 30, 2012 at 6:52 AM, jcbollinger <john.bollin...@stjude.org> wrote: > > > On Apr 28, 9:53 am, Philip Brown <p...@bolthole.com> wrote: > >> Sadly, the chances of getting all sysadmins to be dilligent about creating >> packages are pretty much zero. >> They only want to deal with premade downloadable packages. > > > It sounds like you might be able to split this into two parts. Surely > there aren't many of those 5800 files that your sysadmins routinely > change (else they're acting as developers, not admins). Build a > package or packages of the binaries, containing also whatever default > configuration files are appropriate.
I've already said that converting modified files to packages, was not an option. > And if your admins do not appreciate the advantages of avoiding > installing unpackaged binaries then you need better admins. whether or not that is true, unfortunately does not bring me closer to a usable techical solution :( -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
