Hi all, I think there are a few classes or subsystems in Puppet that could, and maybe should, be extracted into separate projects so they can be more widely used; at worst, they could at least be shared by our other projects. I'd love to be able to pull functional bits out of Puppet and use them elsewhere -- e.g., I'd love to have mcollective, Puppet, PMT, and Facter all share the code that creates their applications.
I'm thinking of, at the least, our graphing stuff and the application classes (plus the Interface classes I'm working on[1]). The problem with doing this, of course, is that it introduces that external code as a dependency, which doesn't really work. I expect the only real choices are to list them as dependencies, or do a kind of vendoring, like we're doing with Event::Loop and JSON. How do other projects solve this? Does anyone have any experience doing so? 1 - https://github.com/lak/puppet-data_cli -- If computers get too powerful, we can organize them into a committee -- that will do them in. -- Bradley's Bromide --------------------------------------------------------------------- Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199 -- 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.
