pm_echovars has strange behaviour lately, looks like it's ignored or so. xmltv ebuilds don't accept it anymore but works completely fine after bypassing perl-module, : src_compile() { ... - pm_echovar=`make_config` - perl-module_src_compile || die "error compiling" + make_config | perl Makefile.PL || die "error configuring" + make || die "error compiling" } src_install() { ... - perl-module_src_install || die "error installing" + make DESTDIR=${D} install || die "error installing" ... } If someone can please be so kind to check this, then thanks. Reproducible: Always
ouch, I missed "perl-module : " from the summary
We need quotes around $pm_echovar
OK, this really breaks every single ebuild that relies on pm_echovar. It was introduced by tove on Mar 6, and I would like to see if fixed quickly. A dirty fix is to change <<< ${pm_echovar} with <<< "${pm_echovar}" so that the end of lines characters get passed to perl Makefile.PL (they are now ignored).
(In reply to comment #3) Hm, maybe I am totally off. > OK, this really breaks every single ebuild that relies on pm_echovar. It was > introduced by tove on Mar 6, and I would like to see if fixed quickly. Are you sure? I tried the old version and it didn't work too. <http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/eclass/perl-module.eclass?rev=1.112> > A dirty fix is to change <<< ${pm_echovar} with <<< "${pm_echovar}" so that the > end of lines characters get passed to perl Makefile.PL (they are now ignored). Did you try this? No difference here.
Arggh. Fixed. Thanks. BTW: Why do you think it is a "dirty fix"?
