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? -- Robert Millan 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." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
