Test::Moose in the perl-Moose package pulls in perl-devel + deps. It would be nice to avoid that on runtime systems. Version-Release number of selected component (if applicable): perl-Moose-0.81-1.fc12.noarch Steps to Reproduce: 1. yum install perl-Moose Actual results: installs perl-devel + deps Expected results: doesn't install perl-devel + deps Additional info: Can we split Test::Moose into a separate sub-package?
Hmmm... yeah, this should be looked at. My initial concern with splitting it off is that I'm not sure how many (or even if any) packages have this as a "silent" test requires.
That's easy enough to check. repoquery, cvs, find, make prep, and grep turn up 41 packages that require perl(Moose), of which 8 also silently require Test::Moose. perl-DBIx-Class perl-Moose perl-MooseX-AttributeHelpers perl-MooseX-Daemonize perl-MooseX-Getopt perl-MooseX-POE perl-MooseX-Role-Parameterized perl-MooseX-Types BTW, perl-MooseX-Daemonize suffers the same problem - it contains Test::MouseX::Daemonize that also brings in perl-devel et al. If only we had rpm with soft-dependencies - perl-Test-Moose BuildSupplements perl-Moose (assuming koji/mock would respect strong soft-deps).
Oof, yeah. I've been wanting soft-deps for ages for reasons along these lines... Ok, so I've done the split and committed/built it in rawhide. The packages soft-requiring it we'll have to add it manually *sigh* unless the package maintainers add it as a test_requires (which given how many of them use Module::Install should be trivial for them to do). I've also filed bugs in rt for the ones above (RT::Client::REST can be _very_ useful) -- except for Moose itself, of course -- so hopefully we'll be seeing test_requires metadata on them soon. I also didn't file one against DBIx::Class as they're still considering Moose to be a "soft" requires. RT#47258 to 63. I'm marking this CLOSED/RAWHIDE; we'll get it out to F-11/10, but not until we're through the current mass-Moose updates, at least.