[Fedora-packaging] ensuring a specific version of python

[Toshio Kuratomi]

On Wed, Aug 10, 2011 at 10:59:30AM -0400, James Laska wrote:
> 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 
> > python".  
> 
> 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.
> 
Rex's answer about the above working but python(abi) being added
automatically for Requires: is right on the button.

Just one note to add: if this is an application rather than a module there is
a python26 package in EPEL5 so it's conceivable that someone could add
enough python26 modules that this was possible.  If it's a module, the
module would need to be renamed python26-MODULE anyway, so that's not a big
deal.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/packaging/attachments/20110810/d743d250/attachment.bin