Skip Menu |

This queue is for tickets about the Any-Moose CPAN distribution.

Report information
The Basics
Id: 70597
Status: resolved
Priority: 0/
Queue: Any-Moose

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.15
Fixed in: (no value)



Subject: Why is Any-Moose depending on Mouse?
Since Mouse is now broken on bleadperl it jumps into the eye that Any-Moose is not a good safety net. It is depending on Mouse and all modules that have chosen to depend on Any::Moose are now untestable, like e.g. MooseX::Log::Log4perl Maybe an oversight?
The point of Any::Moose is to provide you with Moosey sugar when you don't care about the metaobject protocol or extensions. This means that when you use Any::Moose you're generally going to get that sugar from Mouse. Unfortunately the toolchain currently does not support alternatives like "this module depends on Mouse *or* Moose" so we can't just drop the hard Mouse dependency yet.
Why not something like this pseudo code in the Makefile.PL? if eval require Moose prereq = Moose elsif eval require Mouse prereq = Mouse else warn "Neither Moose nor Mouse installed, declareing Mouse a prereq"; prereq = Mouse fi WriteMakefile ( PREREQ_PM => prereq ); What am I missing?
Fixed in 0.16 now on CPAN. rjbs used basically that solution. Thanks, Shawn