remove the INTLTOOL_PERL configure check from clients' configure scripts
Bug #1197875 reported by
Jeremy Sequoia
This bug affects 6 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| intltool |
Confirmed
|
Undecided
|
intltool Developers | ||
Bug Description
Please remove your check and verification of INTLTOOL_PERL from intltool.m4. It serves no purpose as the variable isn't even used anywhere other than your own build system. The installed scripts have the paths coded into their #!
This variable makes package management of intltool-dependent projects difficult. The dependent projects just want an intltool that works. They don't need to know what version of perl it uses. Similarly, intltool itself can be built with any number of different versions of perl that may be on the system. If we let the configure script think it is the default perl, that perl may not have the XML::Parser module, and the configure script will fail even though intltool will work just fine.
Revision history for this message
| Jeremy Sequoia (jeremyhu) wrote | #1 |
| Changed in intltool: | |
| status: | New → Confirmed |
| Changed in intltool: | |
| assignee: | nobody → intltool Developers (intltool) |
Revision history for this message
| Jeremy Sequoia (jeremyhu) wrote | #2 |
Revision history for this message
| Jeremy Sequoia (jeremyhu) wrote | #3 |
Revision history for this message
| Ryan Schmidt (z-launchpad-d) wrote | #4 |
To post a comment you must log in.
What is holding up applying this change? We've been using it in MacPorts to workaround the issue with buggy configure scripts for the past year, but it would be best to get this shipped, so we don't need to autoreconf all of your clients.