Versioning problems in trunk

[David Kastrup]

When installing the Python scripts, those contain references to
directories /usr/local/lib/lilypond/2.13.58 and
/usr/local/share/lilypond/2.13.58 which are outdated.

What's up with that?

./autogen.sh

does not help.

I am now doing "make clean all info" which would appear to put sensible
directory paths in the files in scripts/out (compilation will take a
while to finish, obviously), but is there a point to this behavior?
Actually not even

    rm -rf scripts/out

did the trick: the results after make all again contained outdated
directory versions.

Any possibility of fixing the dependencies in a manner that a changed
version will lead to appropriately changed python scripts?

-- 
David Kastrup