> > You could check (before running emerge) if you see the "3.2.10" anywhere
> > in
> > your environment ("set|less")... or if maybe $PV or $S is set outside
> > emerge somewhere.
>
> Wow, incredible. I never thought to check my environment, but these:
>
> MODULE_VERSION=3.2.10
> MODULE_VERSION_STACK=3.2.10
>
:)
Yes. It's MODULE_VERSION, which is used in perl-module.eclass.
> This was also affecting dev-libs/stfl for me; unsetting MODULE_VERSION
> causes this to succeed.
It can in principle affect many things inheriting perl-module.eclass, I'll
check later what these two do different.
The best workaround is probably to make a short script wrapper for emerge that
unsets the variables and then calls real emerge. A real fix would be to rename
the variable in the eclass, but that would mean fixing 1800 ebuilds...
> Andreas, if this is a bug that needs fixing, let me know who to contact
> get this dealt with.
I'm probably the best address myself, but there is no easy solution. I'll
think about it.
Cheers,
Andreas
--
Andreas K. Huettel
Gentoo Linux developer
kde, council
