Re: git repository for osx-lilypond

[David Kastrup]

Graham Percival <address@hidden> writes:

> On Mon, Feb 13, 2012 at 09:37:44PM +0100, Christian Hitz wrote:
>> 
>> Am 13.02.2012 um 13:36 schrieb Graham Percival:
>> 
>> >> Should I tune osx-lilypad-universal-0.6.tar.gz to be compatible with 
>> >> GUB's 
>> >> installer.py?
>> 
>> Anyway, here is a patched version:
>> http://klarinett.li/lilypond/osx-lilypad-universal-0.6.1.tar.gz
>
> Is that based on the code here?
> https://github.com/gperciva/lilypad
>
> I think we need to have fewer versions of this source code
> floating around.  Could you send a patch for whatever it is you
> did to make 0.6.1.tar.gz ?  or if you only edited the binaries
> after compiling it, could you document the changes you made in
> some file in that repository?

Editing the binaries manually is not really a good option when
distributing GPLed software.

      The "Corresponding Source" for a work in object code form means all
    the source code needed to generate, install, and (for an executable
    work) run the object code and to modify the work, including scripts to
    control those activities.  However, it does not include the work's
    System Libraries, or general-purpose tools or generally available free
    programs which are used unmodified in performing those activities but
    which are not part of the work.  For example, Corresponding Source
    includes interface definition files associated with source files for
    the work, and the source code for shared libraries and dynamically
    linked subprograms that the work is specifically designed to require,
    such as by intimate data communication or control flow between those
    subprograms and other parts of the work.

      The Corresponding Source need not include anything that users
    can regenerate automatically from other parts of the Corresponding
    Source.


-- 
David Kastrup