Re: Dependencies in Lilypond

[Mike Solomon]

Hey all,
    Sorry for the silence w/ respect to this issue: I've been trying to make
due w/o dependencies on my waveform patch and, finally, it looks like I'll
need glpk to make it happen: I was able to dispense with gsl, but the linear
programming algorithms I'm using are too involved to copy and paste a chunk
of code into lilypond.
    To that end, I have three questions:

1)  How would I create a separate branch?
2)  Would it be worth it simply to include glpk in my patch?  It requires no
dependencies itself to compile and it is lightweight, so it could become
"part" of lilypond, but I don't know if that's how things roll chez GNU.
3)  Would it be possible as a middleground of sorts to create an "optional"
dependency in lilypond?  That is, look for glpk and compile the waveforms
stuff only if it is found?  I figured out a way to write that bit of code in
the configure file if said maneuver is ok.

~Mike


On 6/8/10 4:08 PM, "Graham Percival" <address@hidden> wrote:

> On Tue, Jun 08, 2010 at 03:46:47PM +0200, Jan Nieuwenhuizen wrote:
>> Op dinsdag 08-06-2010 om 12:55 uur [tijdzone +0200], schreef Mike
>> Solomon:
>> [cc: lilypond-devel, for the archives]
>> 
>> Hi Mike,
>> 
>>> 1)  Can I add a new dependency, and if so, where would I indicate the
>>> necessity of said dependency?
>> 
>>    configure.in (write/copy and paste a test)
>>    Documentation/included/compile.itexi
>> and in GUB, in
>>    gub/specs/lilypond.py (add as dependency)
>>    gub/specs/libgsl.py (write new recipe)
> 
> However, be aware that we've frozen the dependencies (see issue
> 963), so your patch almost certainly won't be accepted for 2.14.
> That's no reason to halt work, of course; your patch could still
> be merged on to a separate branch it git.
> 
> 
> Alternatively, since this is AFAIK the first time we've tried to
> have a dependency freeze, I could unfreeze it for a week, let
> everybody update everything, and *then* call a freeze.  I would
> still be **extremely** unhappy if lilybuntu broke, but if there
> was an overwhelming desire to add new dependencies, we could
> investigate creating a cut&paste series of apt-get commands to
> add/upgrade the required packages on lilybuntu.
> 
> I don't think we should allow patches that break lilybuntu beyond
> cut&paste fixing until lilybuntu 2 is out, though.
> 
> Cheers,
> - Graham
>