[jkeating at redhat.com: Fedora 11 Mass Rebuild]
Daniel P. Berrange
berrange at redhat.com
Wed Feb 18 11:59:53 UTC 2009
On Wed, Feb 18, 2009 at 11:57:57AM +0000, Richard W.M. Jones wrote:
> I see now, thanks for the explanation.
> Hopefully mingw32-gcc 4.4 will just be a simple matter of replacing
> the gcc tarball and updating mingw32-gcc.spec. However I think I need
> to do a full smock rebuild on my local machine to check there are no
> problems before we push changes to the Fedora repository (since
> backing out the change _if_ it turns out to break is high risk, with
> the F11 cross-compiler feature deadline so close).
> I don't see why the mass rebuild particularly affects this. We might
> just do the update after the mass rebuild has finished, and accept
> there will be a small window (days) when we have gcc 4.4 and
> mingw32-gcc 4.3.
That works too - given that mingw packages only make up 50 out of 7000
RPMS being rebuilt, we can live with building them all again later. The
key is just that we get them all built with 4.4 before feature freeze.
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
More information about the mingw