> Pains me to say this but Gems are designed to solve these problems cos > you can have many versions on a machine and each project can require > the version they wish. > > I'd favor some way to vendor them into our projects so we can maintain > the one we care about internally to each project and upgrade when we're > ready. >
Keep in mind it's often times against package guidelines to ship items that have been 'vendored'. From a systems management perspective, it's the equivalent to static linking binaries. If Puppet started vendoring its dependencies, then EPEL for example, would have to un-vendor them in order to package it for enterprise Linux. It's a slippery slope. I would still be in favor of code reuse, just not so much the vendoring part. Breaking puppet into smaller components is fine. stahnma -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
