Re: [Module::Build] Recursive builds?
Status: Beta
Brought to you by:
kwilliams
|
From: Eric W. <scr...@gm...> - 2006-02-11 18:13:20
|
# from David Golden
# on Saturday 11 February 2006 06:14 am:
>It would seem fairly trivial to add a "recurse_into" parameter with
>directories but then what?
chdir into each one and run $perl, 'Build.PL' or $perl, 'Build' with the=20
same arguments.
>Are each of the directories mirrors of a=20
>normal distribution with their own lib and t directories?
I'm pretty sure that's roughly what ExtUtils::MakeMaker does.
>And how=20
>should building/testing/installing work? =A0Copy all relevant files from
>all recursive directories into a top level blib directory?
No. I think the primary need for recursive builds is to be able to put=20
multiple distributions together and/or separate the Build.PL files to=20
keep things sane. I would also like to be able to trigger MakeMaker=20
builds (unless Module::Build::Inline would be trivial.) I suppose=20
handling the differences between what arguments are supported by=20
MakeMaker makes this hairy.
>Or should there be blibs in each directory?
Yes. You should be able to chdir into each one and run build as if it=20
were a standalone distribution.
>Should top level tests assume the=20
>existence of (and know how to find) files from lower down in the tree?
No. Maybe. If so, it should just add every blib/ to @INC. I imagine=20
that the toplevel tests might be used to test integration of the=20
recursively built modules?
=2D-Eric
=2D-=20
Speak softly and carry a big carrot.
=2D--------------------------------------------------
http://scratchcomputing.com
=2D--------------------------------------------------
|