[fedora-virt] qemu/kvm status

Mark McLoughlin markmc at redhat.com
Fri Feb 13 13:44:42 UTC 2009

On Fri, 2009-02-13 at 10:49 -0200, Eduardo Habkost wrote:

> - First build: all prebuilt binaries tarballs removed from the spec,  
> only
>   native binaries built (using something like %define only_native 1)
> - Second build: added the prebuilt binaries from the first build,
>   no binaries actually compiled, but uses only the prebuilt binaries

Yes, that's what I was thinking.

> We have a problem with any of the above approaches: we don't want to make
> the first build a scratch build (we want to keep the build information
> stored somewhere on Koji),


>  but we don't want this build to be available for the users, as the
> result is an incomplete package.

If you automate it so that the builds happen one after the other, it's
going to be highly unlikely that they e.g. get pulled in by a rawhide

>  I am thinking
> about asking a Koji tag to be created just to store those "intermediate
> build step" RPMs. What do you think?

Perhaps, I'd only worry about it if we ever actually hit problems,


More information about the Fedora-virt mailing list