Re: [Lilypond-auto] Issue 3496 in lilypond: Path expansion in lilypond-book (and others)

[lilypond]

Comment #1 on issue 3496 by address@hidden: Path expansion in lilypond-book  
(and others)
http://code.google.com/p/lilypond/issues/detail?id=3496

> /bin is (rightly from the old days of Unix Edition 6) before /usr/bin in  
> my PATH.

I think that's the wrong order.  /bin is supposed to contain basic (and  
typically statically linked) binaries that work for getting the system up  
and running before /usr or anything else is mounted.  When /usr/bin is  
available, its binaries should usually be preferred over /usr.

> I think the right thing to do will be to add os.path.realpath to expand  
> any symbolic links

No, this strategy won't work.  In a development tree, out/bin/lilypond is a  
symbolic link to lily/out/lilypond.  The former in argv[0] makes it  
possible for LilyPond to find its directories, the latter doesn't.  So  
resolving symlinks will stop _all_ development copies of LilyPond from  
working rather than just those from people having a symlink arrangement for  
/bin and /usr/bin and having the strange order of /bin before /usr/bin.

So the proposed cure is worse than the problem.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings