Re: expected behaviour of configure --prefix vs specialized install paths

[Malcolm Tredinnick <malcolm commsecure com au>]

On Wed, 2003-12-10 at 12:05, Thomas Vander Stichele wrote:
> El mar, 09-12-2003 a las 21:01, Colin Walters escribió:
> > On Tue, 2003-12-09 at 08:12, Thomas Vander Stichele wrote:
> > 
> > > In my opinion any auto* project should be able to pass make distcheck. 
> > > This means, among other things, that they shouldn't install stuff to
> > > non-writable directories.
> > 
> > In Rhythmbox, we do:
> > 
> > DISTCHECK_CONFIGURE_FLAGS = --disable-schemas-install
> > 
> > in the toplevel Makefile.am.
> 
> Does that make "make" rerun "configure" when running make distcheck ?
> Isn't that a tad overkill ? There has to be a better way.

That is exactly the way distcheck is meant to work: it makes a
distribution tarball, unpacks it into a sandbox, runs configure and does
a build. So configure gets run anyway as part of distcheck. It is a
complete check of the experience the user will have when building from
the tarball.

Malcolm