Re: top level: make more dependencies explicit

[Zack Weinberg <zack@codesourcery.com>]

On Sun, Sep 29, 2002 at 02:36:24PM -0400, Andrew Cagney wrote:
> What does the GNU coding standard have to say about the release process?

There are some Makefile targets defined for this purpose, but
personally I think that part of the spec is out of date and should be
ignored.

> I'd also be wary of a ``rewrite'', the top-level stuff iteracts with 
> sub-directories in strange ways.  I think reserving the existing 
> behavior (but perhaphs outside of the Makefile.in) would be a better 
> incremental step.
> 
> Also, how does this compare to GCC's release process.

GCC uses a number of scripts (such as maintainer-scripts/gcc_release)
kept in CVS, but separate from the Makefiles.  I think this is the way
to go.  It prevents exactly this sort of interaction problem.  Also,
the version control policy on release scripts is likely to be
different enough that isolation in separate files will make life
easier.  And it's ever so much easier to write big shell scripts if
you don't have to put backslashes at the end of every line.

zw