Re: updating dependent packages not in rawhide?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2007-12-15 at 17:32 -0800, Chris Weyl wrote:
> Soooo....  Lo and behold, Class::MOP 0.49 is out with significant
> speedups.  Moose is also out with 0.33.  Unfortunately, the new
> Class::MOP breaks Moose < 0.33, and Moose 0.33 breaks on Class::MOP <
> 0.49.  The XS speedups in Class::MOP are on the order of 45% in terms
> of class load time for Moose.
> 
> This gives rise to a question of how to build new versions of 2 (or
> more) packages that are mutually dependent on each other?
> Unfortunately this isn't just a matter of building and then tagging
> both builds in bodhi.  My understanding is that new builds will not
> build against testing (and I wouldn't want to break Moose in testing
> in any case).   I poked around in the wiki but if the answer is in
> there, it successfully kept itself from me.

Just build the new Moose, then email rel-eng and ask them to override
tag it into the buildroot. Then, wait for the repodata to regenerate
(hour or so), then rebuild the new Class::MOP.

When that's done, push them both as a combined update in bodhi.

~spot

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list

[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Legacy Announce]     [Fedora PHP Devel]     [Kernel Devel]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite Information]
  Powered by Linux