On 2011-01-31 10:17, Ohad Levy wrote:
> How about git submodules? extract each component into a separate repo
> which could be pulled in.
> this would allow packaging to be based on submodules too.
> I use it often and find it very useful.
My experience with Git submodules is that they are a pain to use.
After cloning a repository, you have to remember to run 'git init'.
If you checkout a branch (or tag, or any other commit) that has
another version of the submodule, you have to run 'git update' to
actually get that version checked out. And when you do that, Git
connects to that (remote) repository in order to fetch the needed
version, since the history of the submodule is *not* saved in the
local (super-project) repository. You cn forget about doing such
a checkout when offline, or when the submodule repository is offline.
Or has changed URL, or died out, or whatever.
So -1 on Git submodule from me.
/Bellman
--
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.
