Proc::FastSpawn test failure

Marc Lehmann schmorp at schmorp.de
Sat Nov 23 06:27:09 CET 2013


On Fri, Nov 22, 2013 at 12:19:43PM -0700, Darin McBride <darin.mcbride at shaw.ca> wrote:
> I give Configure a "-Dprefix=/real/destination/path/here" and then when it comes 
> time to install, since I need everything separated out for a real install to a 
> different machine, I do "make install DESTDIR=/home/dmcbride/tmp/perl" and 
> then, once all 165+ modules are built to that path, I can cd into DESTDIR and 
> tar everything up to be untarred at the root of the destination system.

There's nothing relocatable about that - you simply break your perl
installation that way.

> But when I run /home/dmcbride/tmp/perl/real/destination/path/here/bin/perl -
> MConfig -E 'say $Config{perlpath}', I get /real/destination/path/here/bin/perl - 
> which is where everything will eventually go, but isn't yet.

That's because you haven't relocated your perl, you just moved it
away. That jsut destroys your install, it doesn't relocate it.

I don't think cpan modules should support obviously broken installs - there
is a perfectly fine mechanism to find out which path to perl is the correct
one, and modules shouldn't need to second-guess that one in their testsuite.

You might want to look at the various windows perls which are relocatable,
to see how they do it.

-- 
                The choice of a       Deliantra, the free code+content MORPG
      -----==-     _GNU_              http://www.deliantra.net
      ----==-- _       generation
      ---==---(_)__  __ ____  __      Marc Lehmann
      --==---/ / _ \/ // /\ \/ /      schmorp at schmorp.de
      -=====/_/_//_/\_,_/ /_/\_\



More information about the anyevent mailing list