On Thu, Jul 3, 2014 at 1:06 AM, Urs Liska <u...@openlilylib.org> wrote: > Our repository has now lived for some time, and I think it is a good thing > to have and maintain. The recent renaming was partially intended to stress > its nature as an _includable_ library (as opposed to the official LSR). But > to make that work for a longer time and to make it scale with an increasing > amount of content I think we now need a fundamental restructuring of its > directory structure.
One thing that would be useful is a way to define dependencies which would be automatically downloaded from some repository. Modern build systems do this (e.g. maven for java). This type of functionality is becoming standard with newer programming languages. I imagine something as simple as: ========= \library "lilyjazz" .... ========= At compile-time it would download the snippet or load it from its local cache. Even something which takes an extra step to request a download would still be useful. In this case the above would give a compile error until you do something like: $ <lilypond package manager> install lilyjazz Of course it can get complicated (versioning, caching, etc.). Just a thought. -----Jay _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
