perl has regrown its dep on perl-ExtUtils-MakeMaker which means that perl-devel is always being pulled in. -devel packages should not be required for a default install
You are suggesting that perl-devel crept in as a requirement of perl-ExtUtils-MakeMaker. We cannot see anything like that. The default package list contains a meta-package named "perl-core," which is proud to deliver "all of the perl bits and modules in the upstream tarball." Indeed, the perl-core requires enlists them all: perl-devel, perl-ExtUtils-*, perl-Test-*, perl-CPAN, and perl-Module-Build. It seems perl-core is part of the default instalation. What is the right solution here? Perhaps perl-core might be split into two parts: One would be named "perl-core-devel" or "perl-apple," would get the original description ("all of the perl...", see above) and would require perl-core and the development packages mentioned above. The other one would be named "perl-core," and would maintain the rest of the current huge requires list. The base install would contain perl-core, but not perl-core-devel. What do you think?
With today's rawhide, that is not the case. perl-core is not listed in comps and the dep tree pulling perl-devel is from [katzj@aglarond comps]$ rpm -qpR ~/trees/rawhide/i386/Packages/perl-ExtUtils-MakeMaker-6.36-38.fc10.i386.rpm |grep devel perl-devel [katzj@aglarond comps]$ rpm -qpR ~/trees/rawhide/i386/Packages/perl-5.10.0-38.fc10.i386.rpm |grep MakeMaker perl(ExtUtils::MakeMaker) [katzj@aglarond comps]$ grep perl-core comps-f10.xml.in [katzj@aglarond comps]$ With F9 gold booted straight off the livecd [root@localhost ~]# rpm -qR perl |grep MakeMaker [root@localhost ~]#
(Oh, I examined obsolete rpms, sorry.) You are right. That unfortunate dependency appeared first in perl-5.10.0-37.fc10. Thank you for your report and for your patience explaining it to me. ;-) After a quick examination, I cannot see anything in the diff which would warrant the change, so I'm afraid it's caused by a change in the build environment. (That is to be confirmed by a scratch build.) Stay tuned.
The problem was caused by enc2xs templates .../Encode/*.e2x, which, unlike the enc2x script itself, were packed in the main perl package. Fixed in perl-5.10.0-39.fc10.