On Fri, 2007-03-02 at 13:05 +0000, Paul Howarth wrote: > Ralf Corsepius wrote: > >> ------- Additional Comments From rnorwood@xxxxxxxxxx 2007-03-01 14:38 EST ------- > >> Balint, > >> > >> Yes, this is related to our splitting out perl-devel in -14 - 'yum install > >> perl-devel' should fix the problem. See bug #226276 > > > > AFAIS, this change seems to break building of any perl-module. > > > > => All perl modules' spec files from now on would require to change all > > perl-modules to "BuildRequire: perl-devel" - > > Are you seriously wanting this? > > > > As this thing doesn't seem to be baked yet[1], and as I don't want to > > see FE-6 and FE-5 being locked out from updates, for now, I will ignore > > this issue on rawhide, i.e. you will likely see broken EVRs between > > rawhide and older FE, on my perl-modules, soon. > > The same issue will affect the grepmail update I'm just about to do as > well. I'm not adding the perl=devel buildreq just yet until a firm > decision on whether all modules have to BR: perl=devel is made. > > > [1] Why is such a massive change being introduced such kind of late in a > > release cycle? IMO, it's way to late, and should be postponed to F8 once > > things have been sorted out. > > It's clearly come about as a result of the perl spec cleanup during the > merge review, but I think splitting out perl-devel at this point is a > bit late given the number of packages that will need changing (unless as > Ralf suggests, the hack of adding perl-devel to the FC7 buildroot is made). I don't see any fault in adding perl-devel to the FC7 buildroot, with the caveat that it will not be there in FC8+. Thoughts? ~spot
