Lars Gullik Bjønnes wrote:
Helge Hafting <[EMAIL PROTECTED]> writes:
| $ ./autogen.sh
| Using automake (GNU automake) 1.9.6
| Using autoconf (GNU Autoconf) 2.59d
| This autoconf version is not supported by LyX.
| LyX only supports autoconf 2.5[2-9].
|
| $ autoconf --version
| autoconf (GNU Autoconf) 2.59d
|
| Hm. LyX only supports 2.5[2-9], this is a 2.59 variety
| and still it isn't accepted. A bad test, or is
| autoconf 2.59d really too different from autoconf 2.59 ?
Where did you get it from?
(a retorical question really)
If you use test software, you must expect to make changes to the apps
you want to build. In this cases you have to add a 'd' or '*' to
autogen.sh
Seems to me that 2.59d is simply a minor update on 2.59.
So why refuse it?
Version tests are usually of the form "above some version number",
not "from this number to that". The latter makes sense only when
a new version is _known_ to be incompatible, the normal approach
is th assume that if the current release is compatble, then the next
one will be too. Especially when talking about minor releases.
Well, if autoconf have a history of breaking compatibility, how about
printing "warning, new unknown autoconf 2.59d could break everything!"
A warning that doesn't actually stop the build, but it points a finger
if something indeed goes wrong. That way you get some testing of
the new autoconf version, and perhaps it can be pronounced safe after
a while. (Or it may be found to be broken of course.)
As it stands, I'll revert autoconf instead so I can compile a newer lyx,
and the lyx sources won't see furter testing with the new autoconf.
Helge Hafting
