# from John Peacock
# on Monday 17 July 2006 07:54 am:
>As a first pass, I can provide a
>Makefile.PL that only installs the pure Perl release;
>
>Does everyone think this is sufficient for now?
I guess. That means nobody with a bare install gets XS until they
explicitly upgrade version *after* installing Module::Build?
Was there a discussion at one point about M::B bundling and/or
bootstrapping its non-core dependencies?
# from David Golden on Monday 17 July 2006 09:35 am:
>Maybe M::B needs to bundle version.pm with it. Or we need to find a
> way for version.pm to install without M::B.
IMO, asking your dependencies to use EU::MM is at least sub-optimal.
This should not be version.pm's problem.
AFAIK, EU::MM never depended on anything that hadn't always been core.
I guess the trade-off is features vs reimplementation unless you bundle
or incorporate some fetch-and-install functionality in the
distribution.
Which would hurt less?
1. bundling dependencies
+ simple
+ predictable
- heavy (but not that heavy)
- requires recursive build support?
- additional packaging-time task/checks required (automate)
- "cpan version" would cause two installs of version.pm (big deal?)
2. client-side bootstrapping
- might take more code than recursive builds
- offline builds would be difficult
- fragile (rarely used code in unpredictable situations)
+ reduce .tar.gz file by 47382 bytes
--Eric
--
"Everything goes wrong all at once."
--Quantized Revision of Murphy's Law
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
