Re: organizing multiple repositories with dependencies
- From
PJ Weisberg <pj@irregularexpressions.net>
- Date
- Apr 24, 2012, 21:09 UTC
- Message-ID
- <CAJsNXTmk_A1NxR3ZcuEkEcX-+LyWPq2yY0mdDwAfVLX=Eg9coA@mail.gmail.com>
- In-Reply-To
- <CAE1pOi2KgeLPg7UVRP7dbqLFJErsKUx22Mi5aSkphy7KMJhoUQ@mail.gmail.com>
On Tue, Apr 24, 2012 at 11:54 AM, Hilco Wijbenga <hilco.wijbenga@gmail.com> wrote:
Show 14 quoted lines
> On 24 April 2012 10:17, <dag@cray.com> wrote: >> Hilco Wijbenga <hilco.wijbenga@gmail.com> writes: >> >>> I'm assuming that if you have subproject S in umbrella project U and a >>> branch "topic" in U then that same branch should exist in S. >> >> No, I think that is actually very rare. If topic branches really should >> be mirrored then U and S should be one repository. They are too closely >> coupled to be separated. But see the but about git-subtree and topic >> branches below. > > Too closely coupled? I do not think breaking up a project into a set > of libraries makes everything tightly coupled. I would argue the > opposite. :-) Anyway, you answer my concern below.
Indeed. But when you make a branch in your main project, wouldn't you usually still want to use the master branch of the libraries? Or if there's an experimental branch in a library and you want to use that branched version, wouldn't you still use the master version of all the other libraries? What if you have two projects that both use a library, but are otherwise unrelated? If you create a branch called 'hotfix' in one project, do you automatically find your library version switching to an unrelated 'hotfix' from another project?
-PJ
Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced.