Re: Transition proposal: pkg-config to pkgconf
Andrej Shadura left as an exercise for the reader: > It seems like the proposal went mostly unnoticed. Any comments, ideas, > anything? fwiw, every time i've looked at a difference between the two, pkgconf was superior in every way. i've worked with the primary author, ariadne conill, on some Alpine stuff and some Notcurses stuff, and she's as competent and sedulous as they come. i'd love to see this transition, and appreciate you working on it. -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe.
Re: Transition proposal: pkg-config to pkgconf
On 2022-08-29 15:38 +0200, Andrej Shadura wrote: > Hi, > > It seems like the proposal went mostly unnoticed. Any comments, ideas, > anything? I have an interest as having been responsible for the pkg-config crosswrapper stuff some years ago, but have not been taking much notice recently. If everything you said in your mail is true (the new one is a superset and better in every way, and the cross stuff will still work but in a less complicated way) then it sounds like a sensible plan. I must admit to having never heard of pkgconf before today, but you are a sensible chap so I assume this is indeed all as you say it is. > Meanwhile, I have uploaded an updated version of the package which dropped > the crosswrapper, and instead uses the "personalities" feature to implement > its functionality. The package also no longer needs a dpkg hook, as it ships > a per-architecture symlinks in arch-specific packages. I would like to understand how the cross stuff works with this personalities thing, but it may be a while before I get round to it. Again I shall assume that you know what you are doing :-) If Helmut is happy then I'm sure it's good. Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Re: Transition proposal: pkg-config to pkgconf
On Wed, 31 Aug 2022 at 16:53:48 +0200, Andrej Shadura wrote:
> The idea is that e.g. pkgconf:amd64 provides
> /usr/bin/x86_64-linux-gnu-pkg-config, which is a symlink to pkgconf,
> and /usr/share/pkgconfig/personality.d/x86_64-linux-gnu.personality,
> which defines DefaultSearchPaths and SystemLibraryPaths to be appropriate
> values for amd64.
Beware that to be compatible with what pkg-config does (and what
PKG_CHECK_MODULES wants), the cross-tools need to be prefixed with a
GNU tuple, and *not* a multiarch tuple. So in particular for i386, you
will need to provide /usr/bin/i686-linux-gnu-pkg-config (and presumably
a matching personality).
In other words, this is ${DEB_HOST_GNU_TYPE}-pkg-config and not
${DEB_HOST_MULTIARCH}-pkg-config. This matches the pattern used for
other cross-tools like compilers.
You might want to *also* provide ${DEB_HOST_MULTIARCH}-pkg-config, if they
differ, but it is ${DEB_HOST_GNU_TYPE}-pkg-config that is canonically used.
smcv
Re: Transition proposal: pkg-config to pkgconf
Hi,
On Wed, 31 Aug 2022, at 22:25, Simon McVittie wrote:
> Beware that to be compatible with what pkg-config does (and what
> PKG_CHECK_MODULES wants), the cross-tools need to be prefixed with a
> GNU tuple, and *not* a multiarch tuple. So in particular for i386, you
> will need to provide /usr/bin/i686-linux-gnu-pkg-config (and presumably
> a matching personality).
>
> In other words, this is ${DEB_HOST_GNU_TYPE}-pkg-config and not
> ${DEB_HOST_MULTIARCH}-pkg-config. This matches the pattern used for
> other cross-tools like compilers.
>
> You might want to *also* provide ${DEB_HOST_MULTIARCH}-pkg-config, if they
> differ, but it is ${DEB_HOST_GNU_TYPE}-pkg-config that is canonically used.
Thanks for pointing out, that’s something I need to fix.
--
Cheers,
Andrej
