Re: Providing libpq explicitly

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Devrim Gündüz <devrim(at)gunduz(dot)org>
Cc: pgsql-pkg-yum <pgsql-pkg-yum(at)postgresql(dot)org>, Talha Bin Rizwan <talha(dot)rizwan(at)enterprisedb(dot)com>
Subject: Re: Providing libpq explicitly
Date: 2016-10-10 07:20:49
Message-ID: CAMsr+YFjOK93eC2B7gQ-XrbDqU2nifJi3i0hvBjcc3Xe7V-xXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-pkg-yum

On 10 October 2016 at 14:44, Devrim Gündüz <devrim(at)gunduz(dot)org> wrote:
>
> Hi Craig,
>
> Around Sep 2014, I committed a patch of yours that remove explicit
>
> Provides: libpq.so
>
> from the PostgreSQL RPMs, for 9.4 beta2. Do you remember the reason behind
> this?

Honestly, I don't have the foggiest anymore.

> For 3rd party apps that depend on specific version of libpq (I mean like "libpq
>>= 9.1", not libpq.so.5) are broken now. Would you mind if I put it back to the
> community RPMs?

I'd argue that such packages are simply incorrectly packaged. There's
no such thing as "libpq 9.1".

They should be using rpm's automatic library dependencies to ensure
that dependency, and shouldn't declare an explicit dependency.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-pkg-yum by date

  From Date Subject
Next Message Devrim Gündüz 2016-10-10 07:28:17 Re: Providing libpq explicitly
Previous Message Devrim Gündüz 2016-10-10 06:44:06 Providing libpq explicitly