http://qa.mandrakesoft.com/show_bug.cgi?id=4698
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2003-12-08 15:08 -------
For the record, I'd like to remind you that this problem exists because the
people at autoconf decided it was not a good idea to release a 2.5x version
still compatible with 2.13, or if it was too hard (redesigning code from scratch
for example) neither was a good idea to add the old 2.13 code in 2.5x and
fallback on it on clever circumstances.
Guess what? I had to write that dirty script to detect which version to run
because introducing 2.5x broke 2/3 of our distribution, something like 2,000
packages (and, no, especially considering the error, erhm, "messages", of m4 or
autoconf, fixing them all was not an option).
I documented this in the %description tag of both rpm's, I've put a bold warning
in the documentation of each package (files that can be found under
/usr/share/doc/%package-%version). There is even the same information in the
info-file of 2.5 as you noticed. I've forgotten to duplicate another time the
same information in the info-file of 2.13, can you understand that? Now I beg
your pardon, I'll flagellate, I promise!
Fixed in 2.13-18mdk.
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
The autoconf 2.13 is two years old by now, but it still
the default for typing `info autoconf`. This is misleading
and it makes users get WRONG INFORMATION about the
capabilities of autoconf, which in turn makes them turn
TO US on the AUTOCONF MAILINGLISTS with questions that
have been fixed years ago. Cumbersome.
A quick fix would include a PATCH to the documentation that
adds a hint to the newer docs and newer 2.5x package of
autconf. That patch does ALREADY EXIST in the autoconf-2.5x
package, it does currently patch the newer (!!) autoconf
info document to include a hint to the old autoconf pages.
This is, errr, not quite the best thing, it should be the
other way 'round, or just to do it to both autoconf pages.
Action Plan:
- take the autoconf-2.5x info-page patch
- put into autoconf (archaic 2.13) spec
- be happy
For the record, that info-pages patch adds the following
section to the top of the autoconf*.info entry page,
even w/o modification it carries valuable information:
-+-+-+-+- IMPORTANT, PLEASE NOTICE ===> this version is meant to
coexist with autoconf-2.13 (for backwards compatibility); to that end,
the various binaries are actually linked to a script which decides
which version to execute. It tries to be clever and will execute 2.5x if
`configure.ac' is present, or if `configure.in' contains AC_PREREQ and
the value's 3 first letters are stringwise greater than '2.1'. You can
also manually select it by providing the environment variable
WANT_AUTOCONF_2_5 set to `1' (use WANT_AUTOCONF_2_1 if you want the
2.13 version). But do not invoke directly autoconf-2.5x or other
sub-utilities with the -2.5x suffix.
