Trond Eivind Glomsrød writes:
> Exactly what bug are you thinking of?
>
> The current build process tries to detect your current version of
> python and build for that..
The RPMs Lamar distributed had Python 1.5 hardcoded. If you fixed that in
the meantime, my apologies.
--
Peter Eisentraut
On Friday 13 July 2001 14:47, Peter Eisentraut wrote:
> Lamar Owen writes:
> > But I will reiterate that the prebuilt binary RPMs are built for _stock_
> > RedHat (and hopefully the systems used to build the non-RedHat binaries
> > are stock, as well).
> Maybe the directory naming on the ftp site
Lamar Owen writes:
> But I will reiterate that the prebuilt binary RPMs are built for _stock_
> RedHat (and hopefully the systems used to build the non-RedHat binaries are
> stock, as well).
Maybe the directory naming on the ftp site should indicate this. For
instance, I see v7.1-Mandrake, that
On Friday 13 July 2001 12:20, Peter Eisentraut wrote:
> Keith F Irwin writes:
> > But redhat 7.1 comes stock with python 1.5.2. For various reasons, I've
> > upgraded to Python 2.1, which DOESN'T replace python 1.5, but, rather,
> > installs the new version along side. In other words:
> > /
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Keith F Irwin writes:
>
> > But redhat 7.1 comes stock with python 1.5.2. For various reasons, I've
> > upgraded to Python 2.1, which DOESN'T replace python 1.5, but, rather,
> > installs the new version along side. In other words:
> >
> > /us
> > What does it mean to hardcode the pyver variable on top of the file?
>
> Look at the specfile, and you'll see the an attempt to autodetect the
> version of python installed. You can hardcode the result...
AH! The Spec file! Okay, THAT I get. :) Excellent. That'll work
nicely.
Keith
>
>
