Le mardi 26 juin 2012 à 10:17 +0100, Phil Holmes a écrit : > We have 2 options: > > 1) Create $LILYPOND_GIT/Documentation/snippets as a straight copy-and-paste, > which is very simple, but proliferates directories in git, and means that an > update should mean deleting all the subdirectories of > $LILYPOND_GIT/Documentation/snippets _EXCEPT_ /new before copying over the > snippets; or
This would create hassle with tarball rolling (i.e. specifying subdirectories in Documentation/snippets/GNUmakefile and makefiles in subdirectories just for distributing files!). > 2) Use a script to update $LILYPOND_GIT/Documentation/snippets. This > deletes all the old snippets except /new; reads all the snippets in the > tarball; adds the correct lsrtags and writes the resulting output to > $LILYPOND_GIT/Documentation/snippets. I'm happier with 2), this is what makelsr.py already does among other things. We could also have makelsr.py write in $LILYPOND_GIT/Documentation/snippets convert-lyed incarnations of snippets and copy snippets from Documentation/new; with this scheme, the only difference with existing scheme would be that the inclusion of translations in .texidoc files would not be done in source files. Cheers, John _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
