Elaborating on what I said in the other mail and trying to put it mostly
together in one place:
# from David Golden
# on Thursday 10 September 2009 12:57:
>(1a) Should bundling modules into inc/ happen in $source or $distdir?
$distdir
>(1b) For either choice in #1a, how should the behavior of “bundle_inc”
>change depending on whether $source/inc exists or is missing?
See my previous mail.
>(2a) Should inc::latest work for any module at any depth in a
>directory bundled in inc/?
I think it should only look for it in inc/inc_$mod - where $mod =~
s/::/-/g.
>(2b) Should modules to bundle be based on configure_requires or
>modules actually loaded by inc::latest or by some other specification?
> How does this depend on the answer to #2a?
Only the modules that were loaded. They should then be written into
configure_requires.
>(3) How should we map from a module name to bundle to a set of module
> files?
Use the packlist. Only the packlist. If the packlist doesn't work, fix
the packlist.
>(4) Should inc::latest emulate “require” or “use”? If “use”, should
>it be able to handle the full semantics of “use MODULE VERSION LIST”
>and how?
How about the string '()'? This is a pain regardless of how you do it
because it can't parse exactly like use.
--Eric
--
Atavism n: The recurrence of any peculiarity or disease of an ancestor
in a subsequent generation, usually due to genetic recombination.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
