# from David Golden
# on Monday 07 September 2009 14:40:
>> use lib 'inc';
>> use latest 'Module::Build';
>...
>M::I installs an "inc::Module::Install" into the normal @INC libraries
>that allows bootstrapping the inc/ directory. It might be worth
>exploring that kind of approach.
I would prefer to avoid its assumption about @INC ordering and contents.
It's tempting though to go with the one-line can't-get-it-wrong
incantation vs the two-line asking-for-trouble one. I suppose if the
installed inc/latest.pm can always sort things out then maybe the only
place we hit a wall is when there's no '.' in @INC at all.
> use inc::Module::Build::Bundled;
>
>Where that would be a subclass of M::B that sets up the necessary inc/
>manipulations.
I don't think we want to go down the subclass cul de sac.
The nice thing about the (to be renamed?) latest.pm approach is that it
isn't specific to Module::Build and keeps these mechanisms from getting
tangled. It also allows you to have an inc-latest dist on the CPAN
with its own set of dependencies (no backwards bootstrapping bendovers
needed for developer tools.) The only constraint is in the as-shipped
inc/latest.pm.
--Eric
--
Introducing change is like pulling off a bandage: the pain is a memory
almost as soon as you feel it.
--Paul Graham
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
