Summary: | dev-perl/Email-Sender-0.120.2-r1 should depend on dev-perl/MRO-Compat - Can't locate MRO/Compat.pm in @INC | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul McDermott <pmcdermott98> |
Component: | [OLD] Development | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | Sergiy.Borodych |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paul McDermott
2014-10-08 10:22:47 UTC
IMHO Seems like this is not Email::Sender issue.
Look at
> at /usr/lib/perl5/vendor_perl/5.16.3/i686-linux-thread-multi/Class/MOP.pm line 15.
AFAIK Email::Sender use Moo.
And seems like you have Moose also (because Class::MOP comes with it).
And Moo try to load Class::MOP which require MRO::Compact.
So the question:
How was installed all those modules?
Do you have them all?
Having Class::MOP installed but not MRO::Compat means you've not installed all the dependencies of dev-perl/Moose properly. dev-perl/Moose provides Class/MOP.pm dev-perl/Moose depends on MRO/Compat.pm Therefore, you appear to have a broken perl install and you need to run perl-cleaner. I have reason to believe you *already* had dev-perl/MRO-Compat installed, however, installed on a previous perl, thus, a re-installation caused it to be installed on your current perl. I take your point that the error was actually coming from Class::MOP, not Email::Sender::Simple. This issue did happen amid the debris of a nightmare migration from perl 5.16 to 5.18, so things could easily have been in the wrong place... As a mere application user I definitely wish that the perl side of Gentoo could be easier. perl-cleaner is not a panacea, especially when perl itself refuses to install.. Thanks for your comments. (In reply to Paul from comment #3) > I take your point that the error was actually coming from Class::MOP, not > Email::Sender::Simple. > Indeed. |