On Wed, 2011-08-10 at 09:24 -0500, Rex Dieter wrote:
On 08/10/2011 09:18 AM, Martin Krizek wrote:
> Is there a proper, 'Packaging Guidelines friendly' way to ensure a specific
version of python?
> Is following fine?
> Requires: python>= 2.6
> BuildRequires: python2-devel>= 2.6
Depends on the context and what you mean exactly by "Specific version of
Just adding a bit more context to Martin's post. Specifically in this
case, the code being packaged no longer runs on python 2.4 (RHEL5). So
we were looking for a way packaging method to ensure this wouldn't land
on any RHEL5 systems, where it's not expected to work.
BuildRequires: python2-devel >= 2.6
will indeed ensure that python3 isn't used, for example.
python runtime deps are generally automatic, with
Requires: python(abi) = ...
being added by rpmbuild. do you have any cases where this isn't the case?