| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Wolfgang Walther <walther(at)technowledgy(dot)de> |
| Subject: | libcurl in libpq.pc |
| Date: | 2025-05-12 10:50:24 |
| Message-ID: | aCHScGj9_dAo-gOM@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Jacob Champion
> Wolfgang reported over in [1] that I've missed a comma when appending
> to the PKG_CONFIG_REQUIRES_PRIVATE list, making libpq.pc look ugly:
>
> Requires.private: libssl, libcrypto libcurl
Is adding libcurl there even the right move? This will make all
programs using pkgconf and linking against libpq require
Build-Depending on libcurl-dev (or more specifically,
libcurl4-openssl-dev). Alternatively, we could make libpq-dev
Depends: libcurl on libcurl-dev. Both solutions seem wrong.
Since nothing in libpq should need curl for compiling, should we drop
it there instead?
Spotted by https://ci.debian.net/packages/h/hoel/unstable/amd64/60438300/
which used PG18. (Which might have more problems as well...)
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-05-12 12:30:03 | Re: Vacuum statistics |
| Previous Message | Roman Khapov | 2025-05-12 10:48:29 | [PATCH v2] Re: Cancel problems of query to pg_stat_statements |