Re: 8.02 rpm error

From: Lamar Owen <lowen(at)pari(dot)edu>
To: pg(at)fastcrypt(dot)com
Cc: Volkan YAZICI <volkan(dot)yazici(at)gmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 8.02 rpm error
Date: 2005-05-20 13:26:36
Message-ID: 200505200926.36803.lowen@pari.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Friday 20 May 2005 07:55, Dave Cramer wrote:
> Well, there's not much discussion here. Other than the fact that a few
> things depend on libpq.so.3.

> Isn't the standard to keep libpq.so.(n-1) whenever you bump the number up ?

Only because libpq versioning has always been an afterthought in the upstream
release process. The RPMset has worked around this in the past by providing
fake previous versions; but it is just an ugly workaround of broken upstream
behavior. This is not a new issue, unfortunately.

That is, symlinks were provided to the new version of the library that
masqueraded as previous versions, but weren't really previous versions. That
can cause it's own broken behavior.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC 28772
(828)862-5554
www.pari.edu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2005-05-20 13:43:50 Re: 8.02 rpm error
Previous Message Berend Tober 2005-05-20 12:29:21 Re: [HACKERS] Inherited constraints and search paths (was Re: