[Module::Build] Re: http://cpanratings.perl.org/dist/Module-Build

[<and...@fr...>]

(CC to Module::Build mailinglist, citing you in full length to provide context)

>>>>> On Tue, 2 May 2006 21:45:25 -0700, "Patrick J. LoPresti" <pa...@al...> said:

  > Using the version of CPAN that ships with Perl -- the one on the
  > just-installed Ubuntu system I have -- setting PREFIX does not work.
  > At least it didn't the last time I tried.  I am sorry, but I forget
  > which exact module had the problem....  I believe it was every module
  > that uses Module::Build.

Pity that you do not remember: a single module would help to find the
problem, whereas the assertion that it is every module that uses
Module::Build can easily be falsified, e.g. I just tried

   perl Makefile.PL PREFIX=/tmp

in the Module-Build-0.28 directory and it worked very well.

  > For example, "install version" ends up
  > bombing out with:

  >  Sorry, PREFIX is not supported.  See the Module::Build
  >  documentation for 'destdir' or 'install_base' instead.

As I said above, it worked very well for me. I tried it specifically
with version-0.59.

  > This happens when the CPAN shell (or the user...) runs "perl
  > Makefile.PL PREFIX=${HOME}/perl".

I repeat, it works for me.

  > I ended up downloading the beta version of MakeMaker and using
  > INSTALL_BASE instead of PREFIX.  But I had to compile and install
  > MakeMaker by hand...  And this is documented nowhere except in various
  > messages on various obscure mailing lists.

Interesting, you do give a hint here that maybe it's a problem with an
old MakeMaker.

  > It would be nice if the Module::Build documentation could address this
  > specific issue, telling users exactly what to do if they want their
  > modules installed under a particular path. I don't even care where
  > they end up exactly; I just want to be able to use the CPAN shell and
  > know that everything will wind up under a specific place.

  > Anyway, sorry if my tone was overly hostile, but I lost enough time
  > figuring out PREFIX years ago...  It was frustrating to lose a couple
  > more hours trying to figure out why it broke.

The best way to avoid that is to write concise bugreports to the
developers. Really. Please try to write a diary during the "couple of
hours" next time you encounter a problem, so that you can back up your
findings with one or two facts.

Thanks,
-- 
andreas