On Wed, 2011-08-10 at 11:01 -0400, Tom Callaway wrote:
> On 08/10/2011 10:59 AM, 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.
> I think this will work:
> Requires: python(abi) > 2.4
> It won't prevent the package from being built for RHEL5. but it sure
> won't install.
Ah, I completely forgot about the "python(abi)" format. This should do
packaging mailing list