fenics team mailing list archive

[Myles English <mylesenglish@xxxxxxxxx>]

Hi Roland,

Roland Siegbert writes:

> Imagine now, there are changes in any of the dependency-repos, than you 
> can fetch them like so:
>
> git submodule foreach git pull origin master
>
> and test against the changes and adjust repo-easing-packaging accordingly.
>
> At my workplace we currently have the problem that we ran into the issue 
> of having one big repo containing many should-be-orthogonal software 
> pieces and now we have to untangle them and integrate them using 
> submodules to ease deployment because it's tangled, heavy to use and clumsy.

Just a note to say that if FEniCS is going to move to git (yes please)
and consider 'git submodule' then you would benefit from looking at 'git
subtree'.  I am just going to quote the man page:

       """
       Subtrees allow subprojects to be included within a subdirectory of the main
       project, optionally including the subproject’s entire history.

       For example, you could include the source code for a library as a subdirectory
       of your application.

       Subtrees are not to be confused with submodules, which are meant for the same
       task. Unlike submodules, subtrees do not need any special constructions (like
       .gitmodule files or gitlinks) be present in your repository, and do not force
       end-users of your repository to do anything special or to understand how
       subtrees work. A subtree is just a subdirectory that can be committed to,
       branched, and merged along with your project in any way you want.
       """

Myles