News for hackers. Stuff that matters.

A comment on Why Google stores billions of lines of code in a single repository (2016). Parent comment

Re:Why Google stores billions of lines of code in a single r... by qquark on Sunday December 10, 2017 @06:15AM (#15890937)
> but it is very unclear how to do it with a distributed repository

Versioning through branching and tagging, while having some drawbacks - at least the fact that you have to DO an operation and that this is not automatic - seem to solve this problem, and are not, in my eyes, a form of monorepo. You globally get more flexibility at the cost of a bit more repo management work.

If the problem is retrieving the right version automatically, externals or submodules should be able to solve this problem. If A and B have no clear dependency direction, a top level repo might help.

[ Parent | on HN ]
Re:Why Google stores billions of lines of code in a single r... by geocar on Sunday December 10, 2017 @09:18AM (#15891452)
> a top level repo might help.

This is the way I generally do it: A repository that represents my system/environment that has submodules for A1, A2, B1, and B2, and scripts for updating the environment.

[ Parent | on HN ]