> I meant implementing a new type like aptrepo there. Actually the best > design decision would be: rename yumrepo as packagerepo, split some of > the code as a provider yumrepo, add new code for a provider aptrepo. But > that isn't easy as pie and it requires ruby knowledge, apt and puppet > internals. This is the elegant, but complex solution. Now I'm balabbering.
You're not blabbering. A new type in Puppet seems like the right idea to me. J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
