Nice work, Geoff. May be they should live on CPAN, so one doesn't need
to remember where to grab them from? e.g. create an empty
Apache::Test::Skeleton::mod_perl(1|2) packages with versioning in those
tars and upload to CPAN?
that's an idea, but kind of a long name :) maybe just
On Jul 7, 2004, at 7:01 AM, Geoffrey Young wrote:
the bug reporting skeleton has become so useful for me (and others)
that I
have created two new skeletons:
I would add a Build.PL with these contents:
use 5.00503;
use Apache::Test::MB;
Apache::Test::MB-new(
module_name =
David Wheeler wrote:
On Jul 7, 2004, at 7:01 AM, Geoffrey Young wrote:
the bug reporting skeleton has become so useful for me (and others)
that I
have created two new skeletons:
I would add a Build.PL with these contents:
use 5.00503;
use Apache::Test::MB;
Isn't that Apache::TestMB?
On Jul 9, 2004, at 11:41 AM, Stas Bekman wrote:
Isn't that Apache::TestMB?
D'oh! Yes! Sorry!
use 5.00503;
use Apache::TestMB;
Apache::TestMB-new(
module_name = 'Apache::Test::Skeleton',
)-create_build_script;
And in fact, to make it more generally useful, I think I'd actually
make it:
use
David Wheeler wrote:
now I think I'll commit a change so that TestMB only outputs the
Generating test running script message if verbosity is enabled. Maybe
you'd like to consider that for TestMM, too?
I think we should try to be consistent with all TestM* frontends, no?
I think we kept this
On Jul 9, 2004, at 1:01 PM, Stas Bekman wrote:
I think we should try to be consistent with all TestM* frontends, no?
Yes.
I think we kept this message, in the same fashion to MakeMaker writing
what does it do. and it's good to tell the user that a utility was
created, so they know they can use
David Wheeler wrote:
[...]
And in fact, to make it more generally useful, I think I'd actually make
it:
use 5.00503;
use Apache::TestMB;
Apache::TestMB-new(
module_name= 'Apache::Test::Skeleton',
license= 'perl',
requires = { 'Apache' = 0,
},
On Jul 9, 2004, at 1:09 PM, Stas Bekman wrote:
There is no Apache.pm in mp2. You probably wanted to say:
requires = { 'mod_perl' = 0,
Right. In fact, it should probably be
requires = { 'mod_perl' = '1.0',
in the MP1 example, and
requires = { 'mod_perl' =
David Wheeler wrote:
On Jul 9, 2004, at 1:09 PM, Stas Bekman wrote:
There is no Apache.pm in mp2. You probably wanted to say:
requires = { 'mod_perl' = 0,
Right. In fact, it should probably be
requires = { 'mod_perl' = '1.0',
in the MP1 example, and
requires = {
oops, thanks for the subject :)
David Wheeler wrote:
On Jul 9, 2004, at 1:01 PM, Stas Bekman wrote:
I think we should try to be consistent with all TestM* frontends, no?
Yes.
I think we kept this message, in the same fashion to MakeMaker writing
what does it do. and it's good to tell the user
On Fri, 9 Jul 2004, David Wheeler wrote:
On Jul 9, 2004, at 1:09 PM, Stas Bekman wrote:
There is no Apache.pm in mp2. You probably wanted to say:
requires = { 'mod_perl' = 0,
Right. In fact, it should probably be
requires = { 'mod_perl' = '1.0',
in the MP1
Randy Kobes wrote:
On Fri, 9 Jul 2004, David Wheeler wrote:
On Jul 9, 2004, at 1:09 PM, Stas Bekman wrote:
There is no Apache.pm in mp2. You probably wanted to say:
requires = { 'mod_perl' = 0,
Right. In fact, it should probably be
requires = { 'mod_perl' = '1.0',
in the
On Jul 9, 2004, at 1:19 PM, Stas Bekman wrote:
It's up to you, since at the moment you are the only MB dev -- you are
the king :)
I'll leave it for now, then.
David
On Jul 9, 2004, at 1:38 PM, Stas Bekman wrote:
It won't work since the version number lives in the package mod_perl.
and most likely you'd want to require a minimal version at some point.
Ah, but this is one of the beauties of Module::Build, my friends.
Behold!
use 5.00503;
use Apache::TestMB;
On Fri, 9 Jul 2004, David Wheeler wrote:
On Jul 9, 2004, at 1:45 PM, David Wheeler wrote:
use 5.00503;
use Apache::TestMB;
Apache::TestMB-new(
module_name= 'Apache::Test::Skeleton',
license= 'perl',
requires = { 'mod_perl' = = 1.0, 1.99,
On Jul 9, 2004, at 2:03 PM, Randy Kobes wrote:
But won't the CPAN indices (which are used by both CPAN.pm
and CPANPLUS.pm) still just recognize one version of
mod_perl.pm? Either the current one associated with mp1, or,
when mp2 is out of development, that associated with mp2
(assuming mod_perl.pm
David Wheeler wrote:
On Jul 9, 2004, at 2:03 PM, Randy Kobes wrote:
But won't the CPAN indices (which are used by both CPAN.pm
and CPANPLUS.pm) still just recognize one version of
mod_perl.pm? Either the current one associated with mp1, or,
when mp2 is out of development, that associated with mp2
Randy Kobes wrote:
On Fri, 9 Jul 2004, Stas Bekman wrote:
Randy Kobes wrote:
[ ... ]
What about requiring 'Apache' for mp1-related modules
(since 'Apache' doesn't exist within mp2), and for mp2
modules, requiring 'Apache2' (which doesn't exist within
mp1)?
It won't work since the version number
On Jul 9, 2004, at 2:23 PM, Stas Bekman wrote:
I don't know how M::B does the version checking, but EU::MM does file
parsing, searching for the $VERSION line, so the version number must
be hardcoded there, unless you do something like:
$VERSION = do { require Apache2; require mod_perl.pm;
David Wheeler wrote:
On Jul 9, 2004, at 2:23 PM, Stas Bekman wrote:
I don't know how M::B does the version checking, but EU::MM does file
parsing, searching for the $VERSION line, so the version number must
be hardcoded there, unless you do something like:
$VERSION = do { require Apache2;
20 matches
Mail list logo
