# from Adam Kennedy
# on Wednesday 21 May 2008:
>The idea with METALOCAL would be that the META.yml would contain the
>regular set of requires/build_requires, but that if the configure
> script was able to tell that it was configuring with a supported CPAN
> client, it would generate it in separate build_requires/test_requires
> instead.
I suppose you could do it that way, but now you've made the situation
where known information which could have been written in META.yml
at 'dist' time is still hidden inside the build code, so you have to
run code to extract what *was* perfectly good static information, which
means that meta harvesters are being fed junk simply because some users
are running some old code and can't be bothered to upgrade.
And what about the 100% declarative build tool which doesn't have a
Build.PL or Makefile.PL, but relies on configure_requires (and maybe
another key or two) to get the META.yml fed into the pbt app? Mythical
it may be as yet, but I see anything which increases its mythicality as
a regression.
--Eric
--
[...proprietary software is better than gpl because...] "There is value
in having somebody you can write checks to, and they fix bugs."
--Mike McNamara (president of a commercial software company)
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
