bug-lilypond
[Top][All Lists]
Advanced

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

Re: lilypond-book is not flavor independent


From: Cláudia Soares
Subject: Re: lilypond-book is not flavor independent
Date: Sat, 28 Mar 2009 12:08:27 +0000


On 2009/03/28, at 11:54, Graham Percival wrote:

On Fri, Mar 27, 2009 at 07:09:28PM +0000, Cláudia Soares wrote:

On 2009/03/26, at 14:54, John Mandereau wrote:

Graham Percival a écrit :
Now, I'll admit that we have very few lilypond users on OpenServer
and Unicos (WTM is Unicos, anyway?!).  And although redhat uses
/bin, as long as there's a symlink it should work.

It sounds like there is no ideal solution, but AFAIK Python is shipped
with all GUB binaries except MacOS X.

I think users should be free to install their programs wherever they
want, if the environment knows what the logged in user wants to run.

Why shouldn't I have my preferred python in PREFIX=$HOME? And other
users in their home dir themselves?

You can have your preferred python wherever you want.  But, as
John pointed out (I had forgotten!), lilypond-book will ignore
your python and use the python that is included in GUB.  This way,
the python scripts are executed using the python version that they
were developed / tested on.

The only problem is that we don't distribute python for OSX, and
OSX has its own issues with python.  I'm not certain /why/ we
don't ship python on OSX, but I *am* certain that it's too
complicated for me to fix at the moment.

Cheers,
- Graham



That's a much better explanation. Thanks.

I don't quite like to have all the apps shipping their own favorite interpreter version... Why not force a version in the path? like
#!/usr/bin/env python2.4


Nevertheless, I can work on that issue concerning the mac osx lilypond. I have one tiger ppc and one leopard intel, so i'll check compat for both OSes and architectures.

Can someone point me to the code's development branch?


Cheers,
Cláudia

|♪♫♪|♫♫|♪♫♪|







reply via email to

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