Hi
On Sun, Mar 21, 2010 at 5:32 AM, Jeffrey jeffreykeg...@jeffreykegler.comwrote:
As far as I can tell
the actual behavior of Module::Build would be more in accord with the
following:
Modules listed in this section are necessary to build and install the
given module. If a listed module is
* Jeffrey jeffreykeg...@jeffreykegler.com [2010-03-22 00:50]:
@Aristotle: Your two one-syllable answers were very useful.
I realised afterwards that the mail reads somewhat gruff rather
than (as intended) amused. Sorry.
An obstacle for me was that Module::Build's actual behavior
seems to
# from Jeffrey
# on Saturday 20 March 2010 20:32:
An obstacle for me was that Module::Build's actual behavior seems to
contradict the documentation in Module::Build::API, which says of
'build_requires' that
Modules listed in this section are necessary to build and install the
given module, but
@Aristotle: Your two one-syllable answers were very useful. The bug
you spotted in your longer answer was from a previous release.
But armed with the knowledge that the voice of experience indicated
that the problem almost certainly lay in my packaging, I went back and
added the Marpa module to
I've got a new module out on CPAN (Marpa::HTML). It requires another
new module of mine (Marpa). I'm getting a lot of NA or UNKNOWN
cpantesters results for Marpa::HTML because of the absense of the
Marpa module at the required version level.
Please note I'm talking about the lastest revs here:
* Jeffrey jeffreykeg...@jeffreykegler.com [2010-03-18 13:00]:
1.) Is this to be expected when a new module (first
non-developer release) is a prerequisite?
No.
2.) Is my set-up still at fault? META.yml, which is created by
Module::build has a Marpa: 0.100 line, which I hoped would
suffice.
