Current best practice for building dependent packages in rawhide?

[Todd Zullinger]

Tom Lane wrote:
> Pardon me if this has been discussed recently, but if I build two
> packages in rawhide and want to be sure the second one is built
> against the new version of the first one, what is the best way?  Do
> I just have to wait for the first one to hit the buildroots, and if
> so how do I tell when it has done so?

In rawhide you can use make chainbuild.  Say you you want to build
whatsit against a new libfoo, commit and tag both.  Then in the
whatsit branch, do make chain-build CHAIN='libfoo'

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To know what is right and not to do it is the worst cowardice.
    -- Confucius

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 542 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20080211/d7e4840f/attachment.sig>