I'd expect a blocker or package.mask to prevent the following: It looks like Email-MIME-blah is deprecated in favor of Email-MIME. * package dev-perl/Email-MIME-Creator-1.456 NOT merged * * Detected file collision(s): * * /usr/lib32/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm * /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-perl/Email-MIME-1.903 * /usr/lib32/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm * /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm It looks like dev-perl/Email-MIME-{Creator,Modifier} both should be deprecated and killed.. .err, I mean be made a blocker of >=dev-perl/Email-MIME. See the URL field for upstream notes on deprecation. ohnopublishing unrealircd4 # qlist -e Email-MIME |grep Attachment ohnopublishing unrealircd4 # qlist -e Email-MIME |grep Content ohnopublishing unrealircd4 # qlist -e Email-MIME |grep Creat /usr/lib32/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm ohnopublishing unrealircd4 # qlist -e Email-MIME |grep Enco ohnopublishing unrealircd4 # qlist -e Email-MIME |grep Mod /usr/lib32/perl5/vendor_perl/5.10.1/Email/MIME/Modifier.pm /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Modifier.pm ohnopublishing unrealircd4 #
The blockers are their; RDEPEND="dev-perl/Email-MessageID >=dev-perl/Email-MIME-Encodings-1.310 >=dev-perl/Email-MIME-ContentType-1.012 >=dev-perl/Email-Simple-2.004 || ( >=dev-perl/Email-Simple-2.100 dev-perl/Email-Simple-Creator ) >=dev-perl/MIME-Types-1.18 !dev-perl/Email-MIME-Modifier !dev-perl/Email-MIME-Creator" DEPEND="${RDEPEND} test? ( dev-perl/Test-Pod dev-perl/Test-Pod-Coverage )" Why do you have both; 32 and 64 /usr/lib32/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm
Here is what I have; qlist Email-MIME /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Header.pm /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Modifier.pm /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME.pm /usr/share/doc/Email-MIME-1.903/Changes.bz2 /usr/share/doc/Email-MIME-1.903/README.bz2 /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/ContentType.pm /usr/share/doc/Email-MIME-ContentType-1.015/Changes.bz2 /usr/share/doc/Email-MIME-ContentType-1.015/README.bz2 /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Encodings.pm /usr/share/doc/Email-MIME-Encodings-1.313/Changes.bz2 /usr/share/doc/Email-MIME-Encodings-1.313/README.bz2
(In reply to comment #1) > The blockers are their; > RDEPEND="dev-perl/Email-MessageID > >=dev-perl/Email-MIME-Encodings-1.310 > >=dev-perl/Email-MIME-ContentType-1.012 > >=dev-perl/Email-Simple-2.004 > || ( >=dev-perl/Email-Simple-2.100 dev-perl/Email-Simple-Creator ) > >=dev-perl/MIME-Types-1.18 > !dev-perl/Email-MIME-Modifier > !dev-perl/Email-MIME-Creator" > DEPEND="${RDEPEND} > test? ( dev-perl/Test-Pod > dev-perl/Test-Pod-Coverage )" > I'm not sure how I avoided hitting this blocker, then. I was using the following command to reinstall these perl modules which were outdated on my machine: emerge -1v Email-{MIME,MIME-{Modifier,Attachment-Stripper},Simple-Creator} -a and portage still outputs the following information and attempts to install the different packages: These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild R ] dev-perl/Email-MIME-1.903 USE="lib32 test" 0 kB [ebuild N ] dev-perl/Email-MIME-Modifier-1.444 USE="lib32" 0 kB [ebuild R ] dev-perl/Email-MIME-Attachment-Stripper-1.313 USE="lib32" 0 kB [ebuild N ] dev-perl/Email-Simple-Creator-1.422 USE="lib32" 0 kB Total: 4 packages (2 new, 2 reinstalls), Size of downloads: 0 kB Maybe it's my fault for using an unstable portage. I'm using 2.2_rc63-r1 (the -r1 just means that I'm using the multilib-portage patch which hopefully makes no difference to these simple perl packages). > Why do you have both; > 32 and 64 > /usr/lib32/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm > /usr/lib64/perl5/vendor_perl/5.10.1/Email/MIME/Creator.pm I use portage-multilib. This means I
(In reply to comment #3) > I use portage-multilib. This means I ... like to trail off in the middle of sentences. OK, I have stuff in both lib32/ and lib64/ because because of how multilib-portage works. This should make no difference for how perl functions, I assume that everything in the lib32 directories will never be touched, needed, or read in. But I don't know completely how perl works. This might mean that if a proprietary application whose source is available and which is only available as a 32-bit binary package which is linked against libperl _might_ utilize the 32-bit perl<->native layer.
