[Fedora-directory-devel] Please review: [Bug 212098] Use autoconf to generate task perl script templates

Richard Megginson rmeggins at redhat.com
Thu Oct 26 02:30:29 UTC 2006

Andrew Bartlett wrote:
> On Wed, 2006-10-25 at 18:14 -0700, Pete Rowley wrote:
>> Andrew Bartlett wrote:
>>> Our current policy is to generate these files for release tarballs, and
>>> for our 'unpacked' tree on samba.org (current SVN checked out).
>> OTOH they are required in order to do:
>> cvs co
>> ./configure
>> make
> Yeah, projects typically end up with an ./autogen.sh to make the right
> innovation of the configure generation tool.
I've found that using autoreconf usually does the right thing.  When I 
change configure.ac/in or Makefile.am or an .m4 file, I always run
autoreconf -vfi
  -v, --verbose            verbosely report processing
  -f, --force              consider all files obsolete
  -i, --install            copy missing auxiliary files
It takes a little longer, but I almost never have conflict or timestamp 
problems.  Plus, it's part of the standard autotools package, and it is 
the way the autoconf/automake manuals recommend rebuilding the autotool 
For some projects, this won't work (e.g. for mozldap, you have to just 
use autoconf-2.13, not autoreconf or autoreconf-2.13).
> Andrew Bartlett
> ------------------------------------------------------------------------
> --
> Fedora-directory-devel mailing list
> Fedora-directory-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3178 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.fedoraproject.org/pipermail/389-devel/attachments/20061025/d359e99c/attachment.bin 

More information about the 389-devel mailing list