1 |
Hello |
2 |
|
3 |
Because of: |
4 |
https://bugs.gentoo.org/show_bug.cgi?id=432848 |
5 |
|
6 |
We discovered an old bug affecting intltool that causes prefix of |
7 |
localedir to be always hardcoded to the same location instead of |
8 |
respecting configure flags. |
9 |
|
10 |
The patch is fixed by intltool upstream in their master branch but still |
11 |
no new version was released including it. Anyway, we now have |
12 |
dev-util/intltool-0.50.2-r1 with the bug fixed. |
13 |
|
14 |
The problem of this issue (and most involving intltool) is that we need |
15 |
to run: |
16 |
intltoolize --copy --automake --force |
17 |
(it doesn't seem to trigger maintainer mode in all ebuilds I have tried, |
18 |
then, doesn't look to require eautoreconf to be run) |
19 |
|
20 |
for all packages to get new and fixed ${S}/po/Makefile.in.in copied to |
21 |
the sources, otherwise bundled file is used and, then, the one unfixed. |
22 |
As it's unreliable to ping all upstreams involving intltool (they are a |
23 |
ton) and this kind of problem will likely re-appear again in the future |
24 |
(since the Makefile.in.in will be fixed in intltool upstream tarball but |
25 |
will take a lot of time to reach all affected packages) we were |
26 |
considering to run above command always at eclass level -> that way we |
27 |
would stop using bundled ${S}/po/Makefile.in.in and, then, we would |
28 |
always use the one provided by our intltool package (that should get |
29 |
fixed and updated more often). |
30 |
|
31 |
Other possible solution would be to use ELT-PATCHES to achieve that, but |
32 |
I am still unsure about how would it work. |
33 |
|
34 |
What are your thoughts? |