| From: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| 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:28:17 |
| Message-ID: | 1476084497.2867.17.camel@gunduz.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-yum |
Hi Craig,
On Mon, 2016-10-10 at 15:20 +0800, Craig Ringer wrote:
> I'd argue that such packages are simply incorrectly packaged. There's
> no such thing as "libpq 9.1".
Well, this actually "works". This means "libpq provided by PostgreSQL 9.1
RPMs", for example, and prevents users to be able to install PostgreSQL < 9.0:
=========================================
Requires: libpq.so >= 9.0
Available: postgresql-libs-8.4.20-6.el6.i686 (base)
libpq.so = 8.4.20-6.el6
You could try using --skip-broken to work around the problem.
=========================================
> They should be using rpm's automatic library dependencies to ensure
> that dependency, and shouldn't declare an explicit dependency.
Then, they would need to generate RPMs for each PostgreSQL version just for
this piece, and it creates other problems.
Regards,
--
Devrim GÜNDÜZ
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-10-10 11:45:36 | Re: Providing libpq explicitly |
| Previous Message | Craig Ringer | 2016-10-10 07:20:49 | Re: Providing libpq explicitly |