On Apr 30, 2008, at 11:55 AM, Luke Kanies wrote: > I wish there were a better way to handle the fact that modules need > to be many to many, and thus each module needs to be in its own > repository. I expect we'll need some kind of tool akin to PRM, or > something that looks a bit like a package manager, to handle merging > changes from our version of a given module to the upstream version, > but I think we'll have to cross this bridge when we come to it.
Looks like this tutorial might help on this front: http://woss.name/2008/04/09/using-git-submodules-to-track-vendorrails/ So maybe it won't be that hard to track other people's Puppet modules using git. -- The people who are regarded as moral luminaries are those who forego ordinary pleasures themselves and find compensation in interfering with the pleasures of others. -- Bertrand Russell --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
