On 1/24/2019 5:44 AM, Knut Petersen wrote:
It would be much easier and faster to set up a lilypond build environment if the tools that are really needed would be submodules
I see. So ideally, people could be starting from scratch, and doing "git clone --recurse-submodules" would bring in everything needed for build.
Now, what happens when a project in a submodule moves in a direction that LilyPond can't immediately follow? Guile after 1.8 for example. Is there a way to keep the submodule at prior state of its repository?
Maybe this "branch" option would do that? <https://git-scm.com/docs/git-submodule#git-submodule---branch> -- Karlin High Missouri, USA _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
