Re: LSR update - a further question

[David Kastrup]

"Phil Holmes" <address@hidden> writes:

> 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

For better or worse, git has no concept of directories as a separate
entity.  There is no such thing as an "empty directory" according to
git, so if you remove all files from a git-controlled directory, git
will attempt to delete that directory by itself when it becomes empty
according to git.  Whether or not that attempt fails (because of
non-version-controlled files remaining in it), git will afterwards no
longer have any knowledge about that directory.

You might want to take this peculiarity into account in your plans.  git
knows no empty directories.

-- 
David Kastrup