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
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
[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
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 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
___