httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: [PATCH] configure.in.in
Date Mon, 20 Dec 1999 22:48:53 GMT
Manoj Kasichainula wrote:
> 
> On Tue, Dec 14, 1999 at 02:07:33AM -0500, Me at IO wrote:
> > Hmm, I just had a thought. If we don't actually recurse into every
> > directory and generate makefiles for all of them, then make clean,
> > make depend, etc. won't work, right?
> 
> For this reason, I'm planning to make the change; I'd like make clean
> and maintainer-mode to work, and I pretty sure it's a requirement if
> we want to be able to ship an Apache tarball with dependencies on
> header files set up properly.
> 
> The change pretty much demands that we have a configure.in.in that a
> sed script fills in with a list of Makefiles; otherwise we'd have to
> manually maintain the list of Makefiles in configure.in, which won't
> be fun.
> 
> Now, we'd probably create configure.in by following the CVS move
> procedure: configure.in -> configure.in.in. I'd like to hear feedback
> (+ or -) on this before I do it, because changing our mind on this
> means that we have to rename the file back, and my understanding is
> that if we want to maintain CVS repository history, this won't be fun.

Actually, I think that's wrong - reinstated files just come back from
the dead, complete with old history and memory lapses. I'm sure I've
tested this.

I find the idea of configure.in.in perversely appealing. But then, I'm a
programmer.

Cheers,

Ben.

--
SECURE HOSTING AT THE BUNKER! http://www.thebunker.net/hosting.htm

http://www.apache-ssl.org/ben.html

"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi

Mime
View raw message