Encode >= 2.13 is a dependency for www-apps/rt-3.8.1
Encode-2.12 is part of dev-lang/perl-5.8.8-r5, but ther isn't a more recent version in portage.
I've created ebuilds as follows:
virtual/perl-Encode-2.12 (the version that's part of dev-lang/perl-5.8.8-r5)
virtual/perl-Encode-2.26 (rdepend on perl-core/Encode-2.26)
I'm requesting that these are added to the tree (or is there a better way?)
Created attachment 163887 [details]
Created attachment 163889 [details]
Created attachment 163890 [details]
It's not done by adding these ebuilds to the tree because of collisions:
* Detected file collision(s):
I am tired and have no solution atm.
> It's not done by adding these ebuilds to the tree because of collisions:
> * Detected file collision(s):
> * /usr/bin/piconv
> * /usr/bin/enc2xs
> I am tired and have no solution atm.
Thanks for looking at this Torsten.
I see this is ugly, but we actually want to overwrite piconv and enc2xs, just as we want to overwrite Encode.pm. So those file collisions aren't a problem in practice.
/usr/bin/piconv and /usr/bin/enc2xs are provided by an earlier version of Encode.pm which is bundled with dev-lang/perl:
# equery belongs /usr/bin/piconv
[ Searching for file(s) /usr/bin/piconv in *... ]
# equery belongs /usr/bin/enc2xs
[ Searching for file(s) /usr/bin/enc2xs in *... ]
# equery belongs /usr/lib/perl5/5.8.8/i686-linux/Encode.pm
[ Searching for file(s) /usr/lib/perl5/5.8.8/i686-linux/Encode.pm in *... ]
Why is it we don't see a file conflict for Encode.pm? Surely that has the same problem with this upgrade?
I'm sorry I don't have the answer - this is beyond my knowledge and experience. But I'd be grateful for any advice, suggestions or help in how to move this forward. Let me know what I can do :)
Any hope of a fix for this?
Maybe upgrading to perl 2.8.9 would be enough (see bug #252824)?
It contains Encode-2.26
perl-core/Encode-2.37 is finally in the tree. It needs >=dev-lang/perl-5.8.8-r8