[Tfug] locating configure info

[Josh Miller]

Call me old fashioned, but I like to also keep a notebook for each
system where I can record such things.

-Josh

On Wed, 2003-11-19 at 21:25, John Gruenenfelder wrote:
> On Wed, Nov 19, 2003 at 09:15:22PM -0700, Scott Denlinger wrote:
> >I'm running Debian Woody, but I decided to install Apache 2.0.47 from
> >source, since I'm not ready to upgrade to testing yet. This is an
> >embarassing question to have to ask, but I seem to have lost the piece
> >of paper I wrote down all the arguments I passed to the ./configure
> >script when I installed 2.0.47. Now that I want to upgrade to 2.0.48, is
> >there a way I can recapture that data? Is there a file or log entry in
> >my 2.0.47 source directory which would have captured that during the
> >installation process?
> 
> Since you mention 'configure', I'm assuming that Apache is using GNU autoconf
> to generate that file.  When you run configure one of the files it generates
> is config.status.  The purpose of this file is to reconfigure the source dir
> the same way as when it was generated.  It also stores the options used gave
> to configure.  Depending on the version of autoconf that generated the
> configure, you can either:
>  1) Run ./config.status --version
>     This will show you what options were used as well as normal version info.
>  2) Look at the top of the config.status file (autoconf < 2.50 I think)
> 
> >I'm relatively new to installing from source, so I haven't mastered all the tricks
> >yet. I'm hoping there's something I can just copy over into my 2.0.48
> >source directory before I run make. Is this possible?
> >
> >And more generally, is there a better way to capture configuration data
> >for programs installed from source than writing it down on paper?
> 
> If you intend to keep the source dir around, then that will suffice.
> Otherwise, just copy the options out and paste them in some other file.  Use
> much less space that way.  :)
-- 
Josh Miller <jmiller at larson-usa.com>
The Larson Company