This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: DOC PATCH to releasing.html: makeinfo requirement
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>, "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 21 Mar 2003 10:29:42 +0100 (CET)
- Subject: Re: DOC PATCH to releasing.html: makeinfo requirement
- References: <Pine.LNX.4.33.0302232120380.11692-100000@kern.srcf.societies.cam.ac.uk>
On Sun, 23 Feb 2003, Gabriel Dos Reis wrote:
> Then [you=Joseph] propose a scheme that makes it possible to "know" the
> required version of makeinfo. Otherwise, you're just encouraging all
> sort of chaos.
Agreed.
In fact, I imagine that ideally we'd have some flag that a release manager
sets and if the version of makeinfo is not sufficient, bails out, instead
of silently omitting the .info files.
Or, probably better, have the release scripts check for .info files and
bail out. In fact, I believe that's what we really should have.
On Sun, 23 Feb 2003, Joseph S. Myers wrote:
> What I'm proposing is something along the lines of
>
> Ensure that you have sufficiently recent versions of makeinfo and bison
> (as detailed in the <a href="install/build.html">installation
> instructions</a>) installed.
That looks good, but having the release script verify these conditions
(and/or that .info files have been generated) appears preferrible to me:
why have a human check something manually if it can be done automatically?
Gerald
--
Gerald "Jerry" pfeifer at dbai dot tuwien dot ac dot at http://www.pfeifer.com/gerald/