lilypond-devel
[Top][All Lists]
Advanced

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

Re: A naive question about permissions in buildscripts/


From: Werner LEMBERG
Subject: Re: A naive question about permissions in buildscripts/
Date: Mon, 08 Dec 2008 07:58:52 +0100 (CET)

> > Then I suggest a new directory `auxscripts'.  It would simplify
> > maintainance.
>
> The only good reason for building most buildscripts is specifying a
> Python binary path at configure invocation different from the
> default Python binary when scripts are run, but this is might be a
> sufficient reason to keep current stuff in buildscripts.  OTOH it
> was convenient for most users to just run the script in buildscripts
> without having to "make -C buildscripts" and call the script in
> out/.

There are two types of scripts:

  . Scripts which are run by the build process.  These *must*
    substitute the Python binary path.

  . Scripts which are run by the lilypond maintainers so that the data
    in the git repository is in good shape.  All such files should be
    moved to a separate directory.

The only question is whether those two subsets intersect.

> Maybe we could create a shell script called auxscript at top of the
> source tree
>
> #!/bin/bash
> make -C buildscripts
> export PYTHONPATH=buildscripts:$(PYTHONPATH)
> exec buildscripts/out/$@
>
>
> It could be then called as
>
> auxscript makelsr LSRDIR
> auxscript check_translation FILE
>
> BTW this would simplify check_translation invocation on individual
> files.
>
> If there is not objection, I'll add this stuff.

This is the wrong solution IMHO.  `makelsr' isn't used during a build,
so it is definitely a candidate for a separate directory.

On the other hand, there are already targets `check-translation' and
`update-translation' in Documentation/GNUmakefile; why not use them?
Again, if they are intended to work on an unconfigured source tree,
both the scripts and the makefile targets should be moved to another
directory.


    Werner




reply via email to

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