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