This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: top level: make more dependencies explicit

From: Andrew Cagney <ac131313 at redhat dot com>
To: Nathanael Nerode <neroden at doctormoo dot dyndns dot org>
Cc: gdb at sources dot redhat dot com, binutils at sources dot redhat dot com,gcc at gcc dot gnu dot org
Date: Sun, 29 Sep 2002 14:36:24 -0400
Subject: Re: top level: make more dependencies explicit
References: <20020929165232.GA27545@doctormoo.dyndns.org> <3D9733C2.2010405@redhat.com> <20020929172608.GA27678@doctormoo.dyndns.org> <3D973C44.6090601@redhat.com> <20020929174544.GA30373@doctormoo.dyndns.org>

The mechanism is very old (it pre-dates me as GDB release engineer). Changing it is going to involve updates to many things - snapshot scripts, release process doco, .... so won't happen overnight.
Mmmm.  I'm going to start rewriting it now. >:-=

What does the GNU coding standard have to say about the release process?

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.

Andrew

Follow-Ups:
- Re: top level: make more dependencies explicit
  - From: Nathanael Nerode
- Re: top level: make more dependencies explicit
  - From: Zack Weinberg
- Re: top level: make more dependencies explicit
  - From: Tom Tromey

References:
- Re: top level: make more dependencies explicit
  - From: Nathanael Nerode

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]