lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Upgrading Python - why not bundle official 2.7 binaries?


From: David Kastrup
Subject: Re: Upgrading Python - why not bundle official 2.7 binaries?
Date: Wed, 19 Dec 2012 10:43:41 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

"address@hidden" <address@hidden> writes:

> On 19 déc. 2012, at 10:18, David Kastrup <address@hidden> wrote:
>
>> Ben Rudiak-Gould <address@hidden> writes:
>> 
>>> On Windows and OS X, I mean; on Linux and FreeBSD I think you could
>>> just demand installation of the appropriate packages.
>>> 
>>> I don't understand what's so unusual about LilyPond's use of Python
>>> that it requires a custom build.
>> 
>> Nothing unusual.  Neither is there anything unusual about LilyPond's use
>> of Ghostscript.  Or GUILE.  Or the Bourne shell.  Or about half a dozen
>> other dependencies.
>> 
>> Leave all of them out from our LilyPond distribution, and the user base
>> on Windows will drop to 5%, while the number of bug reports stays about
>> the same.
>
> I don't think Ben's suggesting to leave them out...it seems like the
> question is why we don't download the binaries directly and bundle
> them with LilyPond.  That'd save having to compile them from source.

Because then all bets are off concerning comparable results.  We
distribute for platforms which no developer really has available.  If we
include unknown code, the resulting problems can't be traced back to
anything under our control.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]