Re: [Monotone-devel] Re: monotone update does not always update MT/options

[Chad Walstrom]

Wim Oudshoorn <address@hidden>  wrote:
> I just checked out the source of 09d27 and discovered that there is
> no ./configure.  

As there should not be, nor should any other configuration or build
generated files.  It's a maintainer or developer's job to create these
for the release of a tarball.  autoconf/automake/autotest are designed
with the end-user/administrator in mind.

> After running aclocal and autoreconfig --install I get the following
> 
> aclocal: configure.ac: 47: macro `AM_GNU_GETTEXT' not found in library

You probably need to install automake as well. (The "AM_" prefixed
macros come from the automake package.)

Personally, I think monotone's use of autoconf/automake/autotest has
made things quite easy to use from a package maintainer's point of
view.  I agree that tests that aren't acted upon are fairly useless,
but they're nice to have when they're needed.

I'm currently trying to migrate GNU GNATS to automake and bring
configure.ac up to date, and honestly, monotone's use of these tools
has helped me template my effort.  Once in place, it shouldn't be too
hard to maintain.  Maybe as I gain more experience with the toolset,
my opinion will change.