David Abrahams wrote:
on Wed Jun 03 2009, Vladimir Prus <vladimir-AT-codesourcery.com> wrote:
David Abrahams wrote:
on Fri May 22 2009, "troy d. straszheim" <troy-AT-resophonic.com> wrote:
I also really worried about this header issue.
Volodya, thanks for the svn:externals suggestion. I'll try to learn more about svn:externals so I can form an opinion.
I said I was "out of ideas", but that was a little disingenuous. This is certainly one of many possible implementations, but I urge caution here. We've been using svn:externals for subproject management for a while, against the conventional
wisdom.
It makes merging even harder, can turn a large difficult-to-merge project into an impossible to merge project. You can end up needing to write tools to wrangle your externals.
Time for Git?
Last time I've checked, it has no externals support whatsoever.
I use git-submodule all the time. Does that not count as externals support?
Oh, looks like it was added after I last read git manual. However, the description does not seem like it's as flexible as svn:external -- which is not required to be pinned to a specific revision. Can you use git-submodule to implement this layout: libs/ program_options/ includes/ boost/ program_options [ same content as includes above, even as 'includes' is modified] ? - Volodya