© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
(In reply to comment #2)
>(In reply to comment #1)
>> Something smells fishy here: since when *forward* compatibility became a
>> requirement for tools like intltool ?
>>
> Because intltool.m4 is copied into configure scripts, and those configure
> scripts will be run on systems with a different version of intltool utilities
> installed.
>
I'm well aware of this part, but I would consider this at most a packaging issue, where upstream has failed to notice the need to bump the required version in configure.ac.
Though I'm not saying upstream already considered and rejected this as a problem, just that I would have mixed feelings about it. Then again, even libtool has issues, if macro and script don't match.