On Sun, Aug 02, 2020 at 11:50:11PM +0200, Helmut Grohne wrote: > Hi Mike, > > On Mon, Aug 03, 2020 at 05:39:23AM +0900, Mike Hommey wrote: > > I'd rather replace nss-config with upstream's. > > Please don't. That makes nss-config subtly buggy. The upstream > nss-config simply calls into pkg-config. In particular, it uses the > unqualified pkg-config. So the behaviour of nss-config becomes dependent > on the architecture you install pkg-config. In practice that means that > means when you install libnss3-dev for a foreign architecture, it will > be broken. And that amounts to breaking cross builds. > > Really, using upstream's is the worst of choices here. Even removing > nss-config entirely would be better as that'd force dependent packages > (of which there are about 12) to properly use pkg-config instead.
Upstream's nss-config uses pkg-config for 3 things: - getting exec_prefix. It's always /usr, independently of the pkg-config you use - getting includedir. It's always /usr/include/nss, independently of the pkg-config you use - getting libdir. This varies dependending on the pkg-config you use, but so does the content of the current nss-config, and as was said up-thread, nothing uses that. So really, using upstream's nss-config wouldn't break things more than they currently are, while it would fix the immediate multi-arch problem. All the while not breaking any reverse-dependency. Mike
