On 25-Aug-05, at 9:15 AM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
Thanks for this info! The problem (and solution) appears on
OSX 10.3.9 as well.
Developers, can we modify scripts/midi2ly.py accordingly?
- Graham
Actually, I'm not sure what the status of this issue is. Technically,
architecture independent stuff should go into /usr/share and binary
libs in /usr/lib/ . Unfortunately, python puts everything in one
directory. Maybe we should install into both share/ and lib/
Well, technically aren't the fonts architecture independent stuff, too?
I don't
have any lily still in /usr/lib/ (I can tell because I'm using the
--prefix=$HOME/usr/pkg/lilypond/ trick; no *lib* in there.)
I think that the overall "where things get installed" design is
separate from
having a working midi2ly. Why not change midi2ly.py to point to share/
for
now, and if we split things into /usr/share/ and /usr/lib/ later, change
midi2ly then.
Cheers,
- Graham
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
