1 |
Andre Lucas Falco wrote: |
2 |
> > > It's possible to use the package.env, described here: |
3 |
> > > http://wiki.gentoo.org/wiki//etc/portage/env. |
4 |
> > > |
5 |
> > > I use this for 2 packages (ghostscript-gpl and orbit), runs flawlessly. |
6 |
> 2013/5/2 Neil Bothwick <neil@××××××××××.uk> |
7 |
> > |
8 |
> > You could, but then you need to remove the settings when automake or the |
9 |
> > ebuilds are fixed. Since a fixed ebuild won't necessarily have a version |
10 |
> > bump, you'd continue using the old version after you don't have to. |
11 |
|
12 |
> Ok, but for me, it's a perspective stuff, the bug ( |
13 |
> https://bugs.gentoo.org/show_bug.cgi?id=451744) has 4 months, and the |
14 |
> packages those i need to compile won't solved. |
15 |
|
16 |
The linked url[1] states that the issue is automake-1.13.1 (and .0). |
17 |
For the fix mentioned, i imagine it's the deprecation warning with -Werror, as |
18 |
the feature is not removed til automake-1.14, which isn't in-tree. |
19 |
|
20 |
I think 1.13.1 should be hard-masked, since it's clearly buggy, and 1.13.2 should |
21 |
be here soon. In any event masking 1.13.1 yourself should be sufficient, for others |
22 |
if not you, as you only have 2 packages failing. |
23 |
|
24 |
Then again, that's what you get for running ~arch ;p |
25 |
|
26 |
Still it's only compilation errors, not broken installs. Not sure what the brouhaha |
27 |
is about: Gentoo users tend to react to compile problems like other distro users |
28 |
react to broken libs, which gives the wrong impression to others (who thus think |
29 |
Gentoo is really unstable in their terms, when the true issue is that some |
30 |
software won't build.) Still, we're only human. |
31 |
|
32 |
Regards, |
33 |
steveL |
34 |
|
35 |
[1] http://www.flameeyes.eu/autotools-mythbuster/forwardporting/automake.html |
36 |
-- |
37 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |