At work, we ship our dependencies with our code. As it turns out,
everyone installs these dependencies in slightly different ways because
no one can *quite* figure out how to configure CPAN to handle this for
us. What we would like, and having it work for both EUMM and
Module::Build, is to make
On Fri, 2007-12-21 at 03:36 -0800, Ovid wrote:
Is there some script out there which will properly configure
CPAN::Config to give us fine-grained control over all of this? Is
there something I've missed in the above?
local::lib is close, although it just changes the PREFIX (for EUMM and
MB).
On Dec 21, 2007 6:36 AM, Ovid [EMAIL PROTECTED] wrote:
At work, we ship our dependencies with our code. As it turns out,
everyone installs these dependencies in slightly different ways because
no one can *quite* figure out how to configure CPAN to handle this for
us. What we would like, and
--- David Golden [EMAIL PROTECTED] wrote:
$ROOT/lib/
$ROOT/arch/lib
$ROOT/bin/
$ROOT/man/man1/
$ROOT/man/man3/
Is this not just --install_base (M::B) or INSTALL_BASE (recent
EU::MM)?
No, --install_base looks like this:
$ROOT/lib/perl5/$Config{archname}
$ROOT/lib/perl5
On Dec 21, 2007 4:25 PM, Ovid [EMAIL PROTECTED] wrote:
No, --install_base looks like this:
$ROOT/lib/perl5/$Config{archname}
$ROOT/lib/perl5
$ROOT/bin
$ROOT/man/man1
$ROOT/man/man3
Which means that you have architecture specific stuff in your lib/perl5
directory. So for a mac
# from Ovid
# on Friday 21 December 2007 03:36:
What we would like, and having it work for both EUMM and
Module::Build, is to make our installation look like this:
$ROOT/lib/
$ROOT/arch/lib
$ROOT/bin/
$ROOT/man/man1/
$ROOT/man/man3/
1. Why like that? (vs a more typical tree that you
