[Build-common-hackers] Bug#534868: Bug#534868: use Makefile as stamp rather than config.status
rmh.debian.bts at aybabtu.com
Sun Jun 28 11:37:40 UTC 2009
On Sun, Jun 28, 2009 at 12:15:26PM +0300, Peter Eisentraut wrote:
> On Saturday 27 June 2009 21:51:24 Robert Millan wrote:
> > The stamp file used for configure target is config.status, which is always
> > present with configure scripts generated by autoconf. However, not all
> > configure scripts are generated by autoconf.
> > A number of projects ship a script with similar semantics that will
> > generate Makefile but not config.status (qemu and mplayer are two notable
> > examples).
> > I recommend that Makefile is used as stamp file instead. This prevents
> > redundant configure runs on such packages.
> But not all configure scripts generate a Makefile either.
> A valid solution may be to provide a variable that allows specifying the stamp
> file. But the default has to stay config.status.
In that case, I think the best solution would be to generate a stamp in CDBS.
Then no matter what configure does, it will always work. How does that sound?
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
More information about the Build-common-hackers