On Wed, 2010-07-07 at 09:34 -0400, Tom "spot" Callaway wrote:
> On 07/07/2010 02:53 AM, Mattias Ellert wrote:
> > tis 2010-07-06 klockan 11:40 -0400 skrev Tom "spot" Callaway:
> >
> >> Lets say you have BuildRequires: foo%{?_isa}. Koji makes the SRPM on a
> >> ppc builder, so %{_isa} is evaluated as (ppc-32). The SRPM is then
> >> handed to an x86_64 builder to build for x86_64, but it cannot meet the
> >> BuildRequires because foo(ppc-32) is not found.
> >>
> >> ~spot
> >
> > This is not how it works.
> >
> > rpmbuild re-evaluates the BuildRequires from the specfile inside the
> > SRPM, it does not use the SRPM's Requires. Having %{?_isa} in
> > BuildRequires tags is perfectly legal - and advisable to have if you
> > want your SRPMs to be buildable in a multiarch environment.
>
> Sorry, my bad, you're correct. rpmbuild does re-evaluate it, perhaps yum
> does not when koji tries to populate the buildroot?
I don't think yum can. It doesn't have any expansion capability for rpm
macros.
-sv
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging
