[Top][All Lists]

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

Re: lilypond-book is not flavor independent

From: Graham Percival
Subject: Re: lilypond-book is not flavor independent
Date: Thu, 26 Mar 2009 21:13:58 +0800
User-agent: Mutt/1.5.18 (2008-05-17)

On Thu, Mar 26, 2009 at 01:26:35AM +0000, Cláudia Soares wrote:
> On 2009/03/25, at 12:10, Graham Percival wrote:
>> On Tue, Mar 24, 2009 at 08:41:04PM +0000, Claudia wrote:
>>> #!/usr/bin/env python
>> See previous discussions about this:
>> http://lists.gnu.org/archive/html/lilypond-devel/2008-03/msg00216.html
>> http://lists.gnu.org/archive/html/lilypond-devel/2008-07/msg00133.html
>> http://www.mail-archive.com/address@hidden/msg12052.html
> As far as I know, all major unixes have /usr/bin/env
> Although we can never guarantee real portability with shebangs, the env 
> binary is the most generic solution.
> If a system does have /bin/env probably the sysadmin already had the  
> need to link it in /usr/bin for some other application.

As you can see from the previous emails, I've been advocating this
for a year.  However, there are some concerns.

> One info source about shebangs can be found at http://www.in-ulm.de/ 
> ~mascheck/various/shebang/

Quote from that website:
 However, the location of env(1) may vary. Free-, Net-, OpenBSD
and some Linux distributions (Debian) only come with /usr/bin/env.
On the other hand, there's only /bin/env at least on OpenServer
5.0.6 and Unicos 9.0.2. (On some other Linux distributions
(Redhat) it's located in /bin and there's a symbolic link from
/usr/bin/env to it.) The env-mechanism is highly increasing
convenience, but cannot strictly assure "portability" of a script.

In practice, env must not be a script, because the #! mechanism
only accepts binary executables (except on very few
implementations like UWIN and Minix). 

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.

And besides, we're in an unstable period right now, so it's the
ideal time to find out if it breaks anything.

John, could you change TARGET_PYTHON to be "/usr/bin/env python"
for all Linux and OSX builds?

- Graham

reply via email to

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