On 11/17/2011 11:04 AM, Chris Tyler wrote: > I agree with going with what we've currently got package-wise. But > saying "we should start building today" or "get Koji running...tomorrow" > is missing the point. > > We're ready to go the moment we have finished these tasks: > - the gcc/glibc issues are resolved > - we've pruned the package sets back to the same core > - every change/patch in those package sets has been upstreamed > - the hub and builders have been successfully set up and tested with > patched koji/rpm/yum etc. > > Work on all these pieces is proceeding in parallel (assuming that > someone's on the gcc/glibc piece (who?)). We're not blocking on any one > piece, but we have to finish these four before hitting 'Go'. The final patch for gcc, for instance, may never make it into F15. Even the armv7hl spec file changes we pushed upstream are only in .fc16 koji builds at this point. If these changes are in FC16 or rawhide but not F15, isn't that good enough? Why not build packages in parallel too? -- Brendan Conoboy / Red Hat, Inc. / blc@xxxxxxxxxx _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
