On Fri, Aug 17, 2007 at 05:00:22PM -0400, Jesse Keating wrote: > On Fri, 17 Aug 2007 22:46:43 +0200 > Axel Thimm <Axel.Thimm@xxxxxxxxxx> wrote: > > > No, what I use in my ancient-dumber-than-kiss chroot builder is to > > extract the BRs, install them and then kickstart any rpmbuild > > machinery. > > How do you extract the BRs? Are you doing it on the host machine, > which could have an ancient rpm, or ancient tools that are needed for > macro expansion? Do you have an Everything install on it, or at least > every piece of software you could expect to run across in a macro? > What about new languages that aren't built for the machine you're doing > the BR extraction from? I think you got me there. But that just means that BRs are not to be macroized. > > > (although isn't it fun that BuildRequires /are/ Requires in the > > > source rpm?) > > > > and you get the fact that these "Requires" are already macro expanded > > so no chicken/egg situation here even if the BRs had had been > > macroized. > > > > So koji could do the following pseudo-code and avoid all troubles: > > > > rpm -qRp foo-1-2.src.rpm | xargs yum --root=xxx --yes install > > rpmbuild --root xxx ... > > Where does the srpm come from? Koji works from cvs tags to ensure that > what you build is actually what came from CVS, so you have to construct > the srpm out of the spec and sources (and oh yeah, sources come from > the lookaside, no trojan sources in random srpm tossed in) So we have trojan detection in CVS and lookaside now? ;) -- Axel.Thimm at ATrpms.net
Attachment:
pgps7sML9ykqO.pgp
Description: PGP signature
-- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers
-- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
