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