Ralf Corsepius <rc040203@xxxxxxxxxx> writes: [...] >> It looks like you unearthed a bug in yum. Reproduced and filed a bug >> here: >> >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231549 >> >> I don't think this should be a blocker for the perl/perl-devel split, > I am not sure about this, because ... > >> since: >> >> o It's a yum bug. >> o perl-devel is still installable with 'yum install perl-devel' >> o In many cases (if the user has something installed that depends on >> something that only perl-devel will provide), the user will get >> perl-devel anyway. >> >> What do you think? >> > > .. this issue renders using > > BuildRequires: perl(ExtUtils::MakeMaker) > (The "correct" BuildRequires for MakeMaker based perl-modules) > > non-functional and (bogusly) forces packagers to resort to using > BuildRequires: perl-devel > or > BuildRequires: perl(ExtUtils::MakeMaker) perl-devel Ok. Seth seems to think he can get that bug fixed for us 'soon', so, assuming it does get fixed soon, I don't think that will be an issue for long. How about I run a build that has a 'Requires: perl-devel' for perl, and remove that for the next one? I just don't want to leave people broken over the weekend. If for some reason Seth can't get this bug fixed for us in F7 time frame, we may end up needing to leave that Requires in for F7, but of course I'd rather not do that. > instead. > > Background: I have another patch to the perl package pending, which > physically separates ExtUtils::MakeMaker, CPAN, Test::Simple and > Test::Harness from "perl-devel". It resolves the issue of some packages > (e.g. mod_perl) to directly depend on perl-devel at run-time. Not sure if I follow - do you mean separates into their own packages, or puts them back into 'perl'? Thanks, -RN -- Robin Norwood Red Hat, Inc. "The Sage does nothing, yet nothing remains undone." -Lao Tzu, Te Tao Ching
