John Mandereau a écrit :
People should never be bored by manually editing snippets in input/new
to write them in input/lsr, as this can be handled automatically by
makelsr, but there are some formatting requirements for stuff in
input/new that are not necessary for regression tests, e.g. tagging.
I fixed makelsr.py so it may be invoked without any directory unpacked
from LSR tarball to inspect; in this case, it doesn't delete anything
in input/lsr, it only updates snippets from what it finds in
input/new, including updating translated texidocs.
As I've started tweaking makelsr.py, let's go on until it does The Right
Thing (tm). Snippets in input/new are added with known people with Git
access, so I don't see it necessary to check them with "lilypond
--safe". Are there any objections with removing this check? This will
allow any doc editor or developer to use makelsr.py to "copy" one or
several snippets from input/new to input/lsr, instead of having to (or
not doing, or partially doing) manual editing.
I'd be glad to take 5 minutes to explain this in the CG, but it
doesn't even explain when you whould write a snippet in input/new, so
it'll take more time than I can afford this week.
It looks like I missed the thread "CG Information on Snippet Handling".
I'm replying there ASAP.
Cheers,
John
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
