LSR update - a further question

[Phil Holmes]

I'm writing a "specification" for the updates for the LSR import and come up 
against an issue that I don't think we've considered, so I'd like thoughts, 
please.

My original assumption would the that the LSR "source" (which I believe 
we've agreed will remain in $LILYPOND_GIT/Documentation/snippets) would 
simply be a copy and paste of the snippets in the docs tarball from the LSR. 
It would be checked for safety before being pushed to git.  I still believe 
this is possible.  However, if this is what we do, then 
$LILYPOND_GIT/Documentation/snippets would have a lot of sub-directories - 
the tarball places a copy of any snippet tagged with, say, "midi" in a midi 
directory.  If it's also tagged with "pitches" a copy also goes in the 
pitches directory.  Currently makelsr uses the list of directories in which 
a snippet occurs to contract an lsrtags tag in the snippet during the 
makelsr run.

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

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 100% happy with either.

--
Phil Holmes