On 24.07.2012 00:43, Ryan Bowlby wrote:
Can anyone comment on their experiences with librarian-puppet or using git superproject with per puppet module repositories? We are in the midst of determining which route is optimal for our environment. It seems like using git superprojects would mean one less new tool for everyone to learn. What then would be the advantages of librarian-puppet?
I've played around with repo (android's git forest manager) but it's just too much complexity for non-developers. I've now switched to everything in one .git and it's just so much easier to manage. Putting external modules in a separate branch and then subtree merge is a viable, albeit still too complex, way for tracking externals.
Best Regards, David -- 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.
