On 09/27/2013 10:53 PM, Curt wrote:
This is a common problem in software engineering. [...]
I assumed so; I don't experience it in the projects I'm currently involved in, but I am sure it is well studied.
For a git-only approach, the *classic* way of handling this - and I haven't yet tried this myself, so I might not be describing this quite right - is to use submodules. So you would have a separate repository for your tweaks, with tags for the different versions you care about. Then you could pull the submodule into your project(s), each pegged at the appropriate version number. However, I think this would require each of your score projects to be in a separate repository.
Makes sense. Probably a branch instead of a full repo per project should also be enough. It's a clean approach, I think, but...
If you keep all your scores in the same repository, [...] you'd probably be stuck with having copies of your tweaks library, with different version numbers in the file names.
...that'll probably be the most realistic option. I feel like a proper approach is simply overkill for my needs. But I cannot judge it yet, I need to try. I'd be glad to be proven wrong... :-)
Thanks, Alexander _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
