Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Mouse CPAN distribution.

Report information
The Basics
Id: 52939
Status: resolved
Priority: 0/
Queue: Mouse

Owner: Nobody in particular
Requestors: t0m [...]

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

Subject: Dependencies in Mouse vary depending where Mouse is built.
Date: Mon, 21 Dec 2009 15:38:06 +0000
To: bug-Mouse [...]
From: Tomas Doran <t0m [...]>
Download (untitled) / with headers
text/plain 938b
The following stanza: if(eval{ require MouseX::AttributeHelpers }){ if(!eval{ MouseX::AttributeHelpers->VERSION(0.06) }){ requires 'MouseX::AttributeHelpers' => 0.06; } } means that MouseX::AttributeHelpers is included as a requirement in the current Mouse release.. Oops - circular dependencies bad.. Something like this: Meta->{values}{build_requires} = [ grep { my $ok = 1; foreach my $module (qw/ MouseX::AttributeHelpers /) { if ($_->[0] =~ /$module/) { $ok = 0; last; } } $ok; } @{Meta->{values}{build_requires}} ]; } just before the WriteAll(); would be a good idea to remove the incorrect build dependencies from META.yml.. I'm happy to fix this myself (if people are ok with this solution?), but wanted to log a bug so that we're all aware of the issue, and any discussion can happen if people think it is needed. Cheers t0m
Download (untitled) / with headers
text/plain 206b
Thank you. Shipped 0.4501 without circular dependencies. (commit: 5e3cb4c022312abf5e3e34cb8bb46a3b4c161e94) I'd like a mechanism that resolves such a problem. "build_requires" seems not sutable.* ---- gfx

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to