Re: Mandrake RPMs rebuilt

Trond Eivind Glomsrød <teg@redhat.com>

From: teg@redhat.com (Trond Eivind Glomsrød )
To: Thomas Lockhart <thomas@fourpalms.org>
Cc: Lamar Owen <lamar.owen@wgcr.org>, PostgreSQL Hackers List <pgsql-hackers@postgresql.org>
Date: 2002-03-06T21:43:18Z
Lists: pgsql-hackers, pgsql-general
Thomas Lockhart <thomas@fourpalms.org> writes:

> (dropped -general from the recipients)
> So far, the only things I had to do were to generate an "mx" RPM for my
> machine, since the eGenix modules are not apparently available from Mdk
> sites.
> 
> Maybe this is one reason:
> 
>     WARNING: Using this file is only recommended if you really must
>     use it for some reason. It is not being actively maintained !
> 
> (from the header of the mxDateTime module :(

It is a standard part of the Python DB API, for better or worse.
 
> > I'll look at your mx RPM's spec and compare to RedHat's -- if a finer grained
> > dependency can be determined, then we can go that route, as the eGenix mx
> > stuff goes by more names than just 'mx'.
> 
> Right. The RH spec seems to have called it "mx2" sometimes, and who
> knows what else it is called once it is packaged (the tarballs have the
> eGenix name in them).

They're set up so you can create mx or mx2, in order to have python
1.5 and python 2.2 installed in parallel.

-- 
Trond Eivind Glomsrød
Red Hat, Inc.