[Bioperl-l] a thought on Bio::Root::Build
Mark A. Jensen
maj at fortinbras.us
Mon Jan 26 11:48:26 UTC 2009
I've got it so this 'core behavior' results only if mbuildpl_arg or
makepl_arg are not already set via MyConfig-- MyConfig
always overrides everything. But still, maybe this is too much fiddling.
Sendu- Let me go back to the drawing board, taking Chris's
comments into closer account.
thanks guys -
----- Original Message -----
From: Dave Messina
To: Mark A. Jensen
Cc: Sendu Bala ; BioPerl List
Sent: Monday, January 26, 2009 4:14 AM
Subject: Re: [Bioperl-l] a thought on Bio::Root::Build
+ # However, if Module::CoreList is available, install
+ # core module updates to the core install set (if the
+ # module was part of the core when the local Perl was
+ # installed...)
I'm not sure I understand this, so forgive me if I'm way off here...
Does this mean that, if an older version of a core module is in a location other than the MyConfig-specified location, the new version of that module will be installed in the same place as the older version?
Foo::Core 1.0 is is /usr/local/lib
user wants to install BioPerl in /home/mylib
BioPerl requires Foo::Core 1.4
then Foo::Core 1.4 will be installed in /usr/local/lib, right?
If that's so, wouldn't that be problematic for users who don't have write perms to places like /usr/local/lib?
More information about the Bioperl-l