Graham Percival a écrit :
I'm not clear about this, either. Actually, if anything
introduction.itely is going to die entirely (as part of the
web-gop stuff).
All right. I can't work on GOP in the 4 coming weeks: I must work on
translaed documentation compilation by translating
node names in source files because the current system has too many bugs;
this alone is already a big task.
And I'm still playing with GUB3 (trying to build it with Python 3 now...).
compile.itely is slated to be removed from AU 1, so in the long
term I think it should be moved to devel/. However, in the short
term I really can't spend the effort requried to make everything
work, so I recommend waiting 1 or 2 months.
OK, in the meantime we at least don't have to worry about compilation
instructions duplicated in the sources.
Do you like the idea of separating compilation instructions for
self-builders and packagers (that must go
in INSTALL too) from instructions for Lily developers?
Cheers,
John
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
