Re: lilypond puts a shared library in /usr/share

2005-10-23 Thread Jan Nieuwenhuizen
Thomas Bushnell writes: > Lilypond installs a shared library in /usr/share, to wit: Fixed in CVS, patch attached. Jan. Index: ChangeLog === RCS file: /cvsroot/lilypond/lilypond/ChangeLog,v retrieving revision 1.3836.2.43 diff -p -u

Re: lilypond puts a shared library in /usr/share

2005-10-22 Thread Thomas Bushnell BSG
Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Pedro Kröger) writes: > >>> This is very bad mojo and a violation of the GNU coding standards, >>> which require that /usr/share is only for architecture independent >>> files. >> >> really? I thought that /usr/local/share was fo

Re: lilypond puts a shared library in /usr/share

2005-10-22 Thread Thomas Bushnell BSG
[EMAIL PROTECTED] (Pedro Kröger) writes: >> This is very bad mojo and a violation of the GNU coding standards, >> which require that /usr/share is only for architecture independent >> files. > > really? I thought that /usr/local/share was for architecture independent > files: > > "The root of the

Re: lilypond puts a shared library in /usr/share

2005-10-22 Thread Pedro Kröger
Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > Lilypond installs a shared library in /usr/share, to wit: [snip] > This is very bad mojo and a violation of the GNU coding standards, > which require that /usr/share is only for architecture independent > files. really? I thought that /usr/local

lilypond puts a shared library in /usr/share

2005-10-22 Thread Thomas Bushnell BSG
Lilypond installs a shared library in /usr/share, to wit: /usr/share/lilypond/2.6.3/python/midi.so (2.6.4 has the same problem.) This is very bad mojo and a violation of the GNU coding standards, which require that /usr/share is only for architecture independent files. Thomas ___