Re: [SPAM] Re: Include ly.music (from Frescobaldi) in LilyPond distribution

[Urs Liska]

Am 20.02.2014 15:41, schrieb David Kastrup:
> Urs Liska <address@hidden> writes:
>
> > I suggest that we include Frescobaldi's new ly.music library into LilyPond.
> > https://github.com/wbsoft/frescobaldi/wiki/Notes-about-ly.music
> > It is a library _and_ a script to process .ly files.
> >
> > For example it is able to construct a DOM for a LilyPond score and
> > generate the .ly file from it. Apart from any other uses one might
> > come up with this would make it easier to create the resulting
> > LilyPond files from midi2ly or musicxml2ly
> >
> > I see the following tasks:
> > - find a suitable place for the library in the source and build
> > (probably below out/lib)
> > - make it accessible (export the path)
> > - incorporate it in the build system
> > - create a straightforward way to pull updates into LilyPond's source dir.
> >
> > What do you think?
>
> Well, issue 1 is that we need the authors to be ok with that.

The author is CCed to my original post, and from all that I know Wilbert 
will certainly be OK with that. Frescobaldi is GPLed, and the new 
library too.
Wilbert invested quite some work to make that library independent from 
other Frescobaldi code and Qt altoghether, particularly for the reason 
that it should be usable outside.

> Issue 2
> is that a typical Frescobaldi/LilyPond installation will then have
> competing installations of the library/script.  Depending on how active
> development on Frescobaldi is, we need to agree on an installation
> scheme that will not get in the hair of either Frescobaldi users and
> non-users.

IISC the library within Frescobaldi wouldn't be visible when running a 
scripts from the LilyPond installation and vice versa because both are 
loading their library files explicitely (i.e. not through a system wide 
search path), LP scripts through ~/bin/lilypond-wrapper.python, 
Frescobaldi from within its main routine.