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
