On Tue, 05 Apr 2005 04:57:50 -0400, Ignacio Vazquez-Abrams wrote:
> On Tue, 2005-04-05 at 04:51 -0400, seth vidal wrote:
> > > Look at these lines in python-amara.spec:
> > >
> > > %build
> > > %{__python}%{pyver} setup.py build
> > >
> > > This requires /usr/bin/python%{pyver}, which is contained in the same
> > > package that provides python-abi = %{pyver}. Since mach would have the
> > > same issue looking for /usr/bin/python%{pyver}, the exact form of the
> > > BuildRequires is unimportant.
> > >
> >
> > no, it's not.
> >
> > mach doesn't look at %build.
> >
> > it's just doing buildreqs in advance for the build.
>
> Yes, you're correct, we've established that. We're not even really
> talking about mach here, we're just discussing why putting a
> BuildRequires on python-abi = %{pyver} makes sense for this package,
> independent of the build system.
It's insufficient and wrong. Looking at python-amara.spec, you do:
%{!?pyver: %define pyver %(%{__python} -c 'import sys;print(sys.version[0:3])')}
%define mainpyver %(%{__python} -c 'import sys;print(sys.version[0:3])')
So, first of all, you depend on %__python, which would be equal to
"BuildRequires: %__python".
Only later you run %{__python}%{pyver} although you don't buildrequire
that binary.
