<<< Date Index >>>     <<< Thread Index >>>

Re: [PATCH] If --with-docdir isn't given, fall back to --docdir. Else



Am 24.07.2009, 12:49 Uhr, schrieb Rocco Rutte <pdmef@xxxxxxx>:

Hi,

* Matthias Andree wrote:

# HG changeset patch
# User Matthias Andree <matthias.andree@xxxxxx>
# Date 1247006816 -7200
# Branch HEAD
# Node ID 6fb746b71758dfe7eda021a119d45b0d7e262f72
# Parent  a3c4b605cfada5be4c9234cbdaa4424206b06fa5
If --with-docdir isn't given, fall back to --docdir. Else warn.

With newer autoconf, this works. But what happens when we tell a
pre-2.59 user to use --docdir which doesn't yet exist in that version?
Can we somehow detect whether --docdir is supported?

Hi Rocco,

You wouldn't be telling this to users, but to developers. Only those checking out from Mercurial will need to run autoconf.

End users get the configure script packaged in the tarball whenever a developer types "make dist" or "make distcheck".

For developers, we can bump AC_PREREQ([2.54]) to AC_PREREQ([2.60]) so that older autoconf versions refuse operation. That would make sure that all "make dist" tarballs support --docdir from that point in time forward.

The borderline question is: when will you consider someone building from the Mercurial repo a "user" and when a "developer"? I'm inclined to call people who check out from Mercurial "developers" - and those can also be required to have autoconf 2.60. It's not that new (over three years now) so I'd say most distributions would have picked up 2.60 or a newer version.

HTH

--
Matthias Andree