Ralf Corsepius <rc040203@xxxxxxxxxx> writes: > On Wed, 2007-05-16 at 11:32 -0400, Robin Norwood wrote: >> Hi, >> >> We've been discussing the perl split and how to minimize disruption for >> users. Warren, spot, and I are seeing about getting the 'core' perl >> packages that have been split into separate RPMs added to the list of >> packages that get installed by default whenever perl is installed. This >> way, most users will still have CPAN + co, but we'll still have most of >> the advantages we wanted from splitting them out in the first place. >> >> This basically changes the 'build/devel' related perl modules from >> opt-in to opt-out for F7. >> >> What do you think? > Wrong move. > > This renders perl-devel into a meta-package and voids/avoids forcing > users to use full BuildRequires. > > I.e. this widely spoils and voids one fundamental aspect the split is > aiming at. I agree, to a point - however, with all this happening so late in the cycle, many people were annoyed at how impactful the changes would be. It's even too late for release notes, so we couldn't hide behind the 'but it was in the release notes...you *did* read the release notes, right?' defense. This way we get to keep the split, and we can remove the packages from the default install early in the F8 dev cycle, giving us more time to warn/badger perl module owners. -RN -- Robin Norwood Red Hat, Inc. "The Sage does nothing, yet nothing remains undone." -Lao Tzu, Te Tao Ching
