Bug 29447 – The newer ExtUtils::MakeMaker ebuilds don't install correctly

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Wayne Davison 2003-09-23 11:18:17 UTC]

The latest SpamAssassin needs at least MakeMaker 6.11, but trying to install it
from portage results in all the perl files getting installed into the portage
tmp dir. This is because older MakeMaker versions don't handle the DESTDIR that
is used in ebuilds for 6.11, 6.13, and 6.15. I'll attach a patch that fixes this.

[Comment 1 Wayne Davison 2003-09-23 11:19:22 UTC]

Created attachment 18214 [details, diff]
Install the perl module in the live directory strucutre.

Fixes the 6.1x ebuilds.

[Comment 2 Robert Coie (RETIRED) 2003-09-23 21:49:49 UTC]

Thank you for bringing this issue to our attention.  I assume you are talking
about SpamAssassin 2.70?  2.60 built fine for me with the existing ebuilds.

With 2.70, I was able to reproduce the problems you mentioned, however, the
patch included here (which may still be a good idea for MakeMaker itself, I'm not
sure yet) made no difference as to whether SpamAssassin 2.70 itself installed
correctly.

So far, the only way I've been able to do that is to change some of the logic
in the perl-module eclass to special-case for later MakeMakers (sigh).

[Comment 3 Wayne Davison 2003-09-24 10:02:54 UTC]

No, I'm not talking about Mail-SpamAssassin 2.70, I'm talking about 2.60
final. I assume you're referring to installing 2.60 from portage, which is a
misnamed ebuild that is really installing 2.60 RC2 or RC3 (I forget). Later
RC releases (and the final release) changed the install to complain and die
if the various INST_* vars that used to be supported were used. This forces
the packager to use the new DESTDIR variable or to manually filter the files
(a kludge that I think should be avoided).

[Comment 4 Michael Cummings (RETIRED) 2003-10-06 03:05:00 UTC]

Wayne,

Is this still an open issue? Mail-Spamassassin-2.60-r1 depends on >= Makemaker
6.11.

[Comment 5 Wayne Davison 2003-10-06 10:20:57 UTC]

The latest ebuilds worked fine for me using the MakeMaker version that comes
with perl 5.8.1.  I have a concern that the updated ebuild that uses DESTDIR
might not work when upgrading from an older perl version, but I have not
tested this using perl 5.6.1 to know if there is an issue or not (and I have
no plans to do so). I'll leave it up to you if you think that more testing
is needed or not.

[Comment 6 Wayne Davison 2003-10-06 10:24:06 UTC]

Sorry, I meant to say that I had a successful install using perl 5.8.0, not
5.8.1 (I haven't forced an upgrade to the newer version yet).

[Comment 7 Neil Katin 2003-10-20 21:59:04 UTC]

I believe I may have found the root cause of this
problem.  See bug 31643 for an explanation
(a bug in /usr/portage/eclass/perl-module.eclass relating
to the test for MakeMaker 6.11)

[Comment 8 Robert Coie (RETIRED) 2003-12-19 22:34:24 UTC]

Believed fixed with current makemakers.