> > I notice Werner recently changed the permissions on a lot of
> > files, including makelsr.py. Can somebody explain how I'm
> > supposed to run these files without using chmod to change the
> > permissions back temporarily?
You shouldn't use the versions in `buildscript' at all. Instead, use
the versions in `buildscript/out' which (a) have all @...@ variables
substituted correctly and (b) have the right permissions.
> Well, you could run
> python makelsr.py
Is there ever need to do that?
> I'm not sure why he changed the permissions, though.
I did this for orthogonality with the many python scripts in this
directory which already had no executable bit -- additionally, it is a
hint to not execute the scripts directly but use the versions in
`out'.
BTW, isn't it an error that `makelsr.py' starts with
#!/usr/bin/env python
instead of
[EMAIL PROTECTED]@
? The same is true for
check_texi_refs.py
check_translation.py
coverage.py
find-superfluous-includes.py
fixcc.py
git-update-changelog.py
manuals_definitions.ly
musicxml_generate_intervals.py
musicxml_generate_keys.py
musicxml_generate_timesignatures.py
mutopia_index.py
readlink.py
tely-gettext.py
translations-status.py
And why does `output-distance.ly' use [EMAIL PROTECTED]@' inspite of
being in `buildscript'? Shouldn't this be [EMAIL PROTECTED]@' also?
Otherwise, there should be a comment...
Werner
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
