[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Explicit interpreter paths considered harmful
From: |
Ludovic Courtès |
Subject: |
Re: Explicit interpreter paths considered harmful |
Date: |
Fri, 06 Nov 2009 22:44:14 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) |
Hi Simon,
Simon Josefsson <address@hidden> writes:
> address@hidden (Ludovic Courtès) writes:
[...]
>> Being a maintainer-only script, I think it should not check for any tool
>> in ‘configure.ac’.
>
> Other maintainer-only scripts (if that is what is implied by being in
> build-aux/) already check for things in configure, for example the
> javacomp script has rather complex tests. So I'm not sure I follow your
> logic.
I was thinking about scripts that are not normally run from a release
tarball, such as ‘announce-gen’, ‘gitlog-to-changelog’, ‘gnupload’,
‘update-copyright’, etc.
Things like ‘javacomp’, ‘depcomp’, ‘missing’, etc., fall into a
different category IMO because they are typically used by the build
system from a release tarball.
Now I agree it’s not all black and white, and one could want things to
be arranged such that ‘pmccabe2html’ will work out of the box from
release tarballs.
Thanks,
Ludo’.