From: Christoph Berg <myon@debian.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Arturo Borrero Gonzalez <arturo@netfilter.org>,
netfilter-devel@vger.kernel.org, eric@regit.org,
Chris Boot <bootc@debian.org>
Subject: Re: [PATCH] build: adjust configure for postgresql 11
Date: Fri, 22 Mar 2019 14:23:59 +0100 [thread overview]
Message-ID: <20190322132359.GC32388@msg.df7cb.de> (raw)
In-Reply-To: <nycvar.YFH.7.76.1903221354530.7557@n3.vanv.qr>
Re: Jan Engelhardt 2019-03-22 <nycvar.YFH.7.76.1903221354530.7557@n3.vanv.qr>
> >> At least in openSUSE, PostgreSQL 11 no longer ships the pg_config
> >> program. Instead, there is has been a pkg-config file around for a
> >> while (also in pg10), so make use of that, by default.
> >
> >Debian ships pg_config. In fact, the same package libpq-dev [0] contains both
> >things:
> >
> >* /usr/bin/pg_config
> >* /usr/lib/x86_64-linux-gnu/pkgconfig/libpq.pc
>
> pg_config is regarded for the server part only, says the respective maintainer.
> https://bugzilla.opensuse.org/show_bug.cgi?id=1120035#c1
That is wishful thinking. It would be nice if all client-side
applications would use pkg-config to interface to libpq, but state of
things is still that pg_config is used by many (most?) of them. That
choice tries to force everyone to switch. If openSUSE wants to fight
that fight, good luck.
`pg_config --libs` should not be used for linking client-side apps.
Thats an artifact from server-side linking.
Christoph
next prev parent reply other threads:[~2019-03-22 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 11:54 [PATCH] build: adjust configure for postgresql 11 Jan Engelhardt
2019-03-21 12:25 ` [PATCH] build: adjust configure for postgresql 10/11 Jan Engelhardt
2019-03-22 9:04 ` [PATCH] build: adjust configure for postgresql 11 Arturo Borrero Gonzalez
2019-03-22 12:55 ` Jan Engelhardt
2019-03-22 13:23 ` Christoph Berg [this message]
2019-04-08 21:43 ` Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190322132359.GC32388@msg.df7cb.de \
--to=myon@debian.org \
--cc=arturo@netfilter.org \
--cc=bootc@debian.org \
--cc=eric@regit.org \
--cc=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.