I've uploaded a *really* alpha Test::CPAN to CPAN:
http://search.cpan.org/~CRAKRJACK/Test-CPAN-0.001/lib/Test/CPAN.pm
I made sure to test Test::CPAN's CPANability (as well as several other
in-progress packages) using Test::CPAN before I uploaded it. ;-)
Ken,
> OK, so for the benefit of CPAN, we can't die, otherwise it won't
> pick up on our dependancies.
>
> But I'd rather not leave everybody at their own peril. :-) So what
> I've done, is when the subclass isn't available, I add "installdirs => {}"
> to the initializer;
>
> --snip--
> eval { require DBIx::Migration::Directories::Build; };
>
> my $build;
>
> if($@) {
> $build = Module::Build->new(%opts, installdirs => {});
> } else {
> $build = DBIx::Migration::Directories::Build->new(%opts);
> }
>
> $build->create_build_script;
> --snip--
This snippet is used as an example in my POD... if you have a better
method to do this sort of thing, I'd really like to document it that way in
the next release (which will also hopefully be a bit more resilient and fill
in a few obvious holes in the module's functionality).
Releasing DBIx::Migration::Directories is blocking on two things: my
having a module that actually uses it properly (this is in progress; an
Apache2-based authentication schema) since I'd like the module to be
well-tested in real life as well as unit-tested before release, and
Module::Build 0.27 being a non-developer release (since the whole
subclassing Module::Build issue is solved then).
Anyways, check 'er out and let me know what you think.
Cheers,
Tyler
