Re: [Module-build-general] Proposal for Module::Build installation dirs

[Ken W. <ke...@ma...>]

On Wednesday, May 14, 2003, at 12:59  PM, Jeff Macdonald wrote:
>
> I use PREFIX and LIB all the time now and I haven't had any problems
> with it yet. Currently M::B doesn't work correctly with builddir or
> sitelib when doing a build test or install (see earlier postings about
> @INC from a fellow subscriber).

You mean the thread where I called M::B's support for local 
installation directories "woefully inadequate"?  I know M::B doesn't 
install (nicely) to arbitrary directories, that's sort of my whole 
point.

What do you mean "builddir" and "sitelib"?

>
> So while there may be magic behind PREFIX, I don't think it is fair for
> the average module builder to have to know specifics about %Config
> either.

In the scheme I proposed, the user has to know *less* about %Config 
than under MakeMaker, because under MakeMaker you have to understand 
how PREFIX interacts with your particular %Config settings in order to 
arrive at the installation paths.  My scheme would just install in the 
obvious way under wherever you tell it to install.


> I need M::B to be able to install stuff outside the system perl tree.
> MakeMaker allows me to do that today using PREFIX and LIB (I set both 
> to
> the same value). All I have to do in my code is add a:
>
> use lib qw(<path specified by PREFIX>);

Yeah, that's why we're working on getting this working.

Incidentally, Module::Build already lets you install to whatever 
directory you want, it's just not pretty:

  perl Build.PL config='siteperl=/foo/bar sitearch=/foo/bar/i386-linux 
installscript=/foo/bar/bin'

  -Ken