# from Sendu Bala
# on Wednesday 15 August 2007 06:48 am:
>I recall having great difficulty getting a Module::Build subclass to
>work correctly (be used) during all possible installation methods if I
>had it in a subdir and had to "use lib 'subdir'". In the end I was
>forced to just have my subclass in the same dir as Build.PL.
That sounds fishy. Was this an early version of M::B where we were
dropping @INC on the floor or something?
I personally use "inc::MySubclass" (and set the package name
accordingly) primarily as an indicator that it is not for external
consumption. (Schwern will now comment about assuming "./" in @INC.)
Perhaps it should be require("./inc/latest.pm") or thereabouts. Though
there might be some reason that this wouldn't hold-up to resume()ing
and etc.
What about external API usage? (e.g. Module::Build->new_from_context())
Would we need to check (from the installed Module::Build via
time-machine) for the inc/latest thing or could we force redefinition
of the M::B namespace via whatever is bundled?
--Eric
--
"I've often gotten the feeling that the only people who have learned
from computer assisted instruction are the authors."
--Ben Schneiderman
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
