On Fri, Mar 23, 2018 at 12:28:14AM +0100, Maren Hachmann wrote:
Am 23.03.2018 um 00:08 schrieb Bryce Harrington:
- I've often seen them using git submodules. For example, MyCroft AI
(smart assistant), pelican (python static website generator) and Atom (editor) use this approach for their (partially user-contributed) extensions (but they do have the extensions in a separate repo, and pull **those** in via submodules).
I seem to remember though that this thought had been rejected due to the complexity it brings. Currently, I wouldn't know how to work with it either, but probably it wouldn't be too hard to find out.
They can make a lot of sense for projects where the primary distribution mechanism is git itself. However, the vast majority of our users are using packages (heck they've probably never even heard of git).
(Part of my earlier concern with git submodules was that in transitioning from bzr to git, we were imposing a bit of a learning curve on our developers, and adding git submodules would increase the complexity of the transition. I suspect now, though, everyone is conversant enough in git, that this particular concern is no longer really a factor. Of course, even so it might end up being more complication than benefit, but I don't think we necessarily need to rule it out just out of principle if we have a good situation where it would make sense.)
Bryce