[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: Han-Wen Nienhuys
Subject: Re:
Date: Mon, 28 Sep 2009 11:54:14 -0300

On Mon, Sep 28, 2009 at 11:40 AM, Graham Percival
<address@hidden> wrote:
> script/ is broken.  I suspect that the general
> out/lybook-db/ thing is the problem -- when I look at self.missing and
> self.added (say, adding a print to line 818 of
> scripts/build/ ), I see tons and tons of files.
> This is confirmed by the following test:
> address@hidden:~/tmp$ ls
> 2.13.3  lilypond-2.13.3-0.test-output.tar.bz2
> 2.13.5  lilypond-2.13.5-HEAD.test-output.tar.bz2
> address@hidden:~/tmp$ find . -name "*.ly" | xargs grep
> accidental-ancient
> ./2.13.3/regression/out-test/11/\sourcefilename
> "/home/lilypond/gub/target/linux-x86/src/"
> ./2.13.5/regression/out-test/b4/\sourcefilename
> "/main/src/gub/target/linux-x86/src/"
> address@hidden:~/tmp$
> I can't see how could track files across such changes.
> So... how are the directories and hashes generated?  If it's
> machine-specific, then we have a hope -- we can't generate a
> comparison between 2.13.3 and 2.13.5, but at least later comparisons
> will be possible.

The files are generated as a md5 (IIRC) hash of the contents, minus
\version, which has always been stripped. Of course, if someone goes
around modifying the templates in, all the hashes
change, and the comparison does not work anymore.  It might be a good
idea to also strip the lp-book boilerplate from the input to the hash.

Han-Wen Nienhuys - address@hidden -

reply via email to

[Prev in Thread] Current Thread [Next in Thread]