python3 rpm macros not available without python3-devel installed. 'rpmbuild
--viewrc' will show you.
So if you use the python3 macros to define another macro and you have no
python3-devel installed, you must fail.
So, how to define, for example, a %py3_ver macro for the major version of
Python3?
On Wed, 2010-09-15 at 18:22 +0800, Robin Lee wrote:
python3 rpm macros not available without python3-devel installed.
'rpmbuild --viewrc' will show you.
So if you use the python3 macros to define another macro and you have
no python3-devel installed, you must fail.
So, how to define, for
On Wed, Sep 15, 2010 at 07:25:49PM +0800, Robin Lee wrote:
For a more concrete example:
https://bugzilla.redhat.com/show_bug.cgi?id=567348
I want to set the python(abi) requirement of the subpackage at buildtime. So,
I
want to set it like this:
Requires: python(abi) = %{py3_ver}
But
When we've talked about this before, in the Packaging Committee we
haven't really cared to stipulate one proper way that maintainers must
follow since there's several possible ways which all seem equally
valid. Inconsistency by itself is not a problem. If it's causing an
issue then it would be
The main point I want to get is to set a proper python(abi) requirement at
buildtime without using hard version number at all.
%{?!py3_ver: %global py3_ver 3.2}
Doing so of course will make the package built. But that uses a hard version
number.
I now suggest the requester to make a phantom file
On Thu, Sep 16, 2010 at 10:03:21AM +0800, Robin Lee wrote:
The main point I want to get is to set a proper python(abi) requirement at
buildtime without using hard version number at all.
%{?!py3_ver: %global py3_ver 3.2}
Doing so of course will make the package built. But that uses a hard
