Re: [Module::Build] Recursive builds?

[Eric W. <scr...@gm...>]

# from alan
# on Monday 13 February 2006 07:18 am:

>When you do a "make test" in a subtree of the build tree, you
> typically want it to use a blib which contains the (most recently
> built) contents of the _entire_ build tree (not just your subtree).

I'm curious as to how many users want this behavior.  I'm thinking that 
anything done in a subtree should be no different than if I were 
building just that subtree.

i.e.  "the recursive build system only recurses down and never up" seems 
like a good design theme.

The behavior you describe doesn't fit the definition of "recursive."

> "make test" in a subtree uses the installed versions of modules
... [which is bad because we want] ...
> to test interactions between modules

I think this sort of testing should be enabled by running "./Build test 
Module-Name" from the toplevel.  This would then do something like:

  1.  run "depends" actions (depth first) for all subdirs
  2.  make a -Ipath/to/Module/blib/lib/ list including all subdirs
  3.  run ACTION_test for the Module-Name dir

I'm sure I've left something out, but the point is to never require a 
build to look upwards from itself.  The toplevel builder should play 
manager to the subdir worker builders, feeding them everything they 
need to know.

There's also something about dependencies in the Build.PL stage.  Maybe 
the toplevel Build.PL could gather all of the META.yml info and inform 
the workers about which dependencies are satisfied by their peers.

--Eric
-- 
But you can never get 3n from n, ever, and if you think you can, please
email me the stock ticker of your company so I can short it.
--Joel Spolsky
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------