Re: [PATCH 13/12] CI: Refresh OpenSUSE Tumbleweed container

[Olaf Hering <olaf@aepfle.de>]

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

Thu, 11 Jul 2024 23:39:42 +0100 Andrew Cooper <andrew.cooper3@citrix.com>:

> configure has to cope with distros taking different naming decisions,
> and while I appreciate that packages may change over time even within a
> distro ...

configure does "pkgconfig --exists something" to probe for some API.
I'm sure noone will rename the pkgconfig files, "something.pc" in this case.

> ... this is just a differently-inconsistent list of names, with some
> very dubious aliases such as `form` and `menu`.

I should have truncated that list of names, 'pkgconfig(ncurses)' and
'pkgconfig(glib-2.0)' are relevant.

> What makes pkgconfig() any more stable than the main package name?

They are supposed to describe some API, and in some cases some functionality.
It does not matter much which package provides the API.

> Why do we want to be treating libraries different to other packages?

Because there is no other namespace to describe functionality.
It was implemented for pkg-config, it exists for some cmake and perl
modules.

> > python3-devel is "special", can be used as is.  
> As an aside, I looked for a python3-minimal or equivalent, and couldn't
> find one.  I take it there isn't one?

I think there are libraries compiled. There is indeed a 'pkgconfig(python3)',
my search just failed to find it. Otherwise, if there are really just .py
files in the tree, 'python3-base' is the string provided by 'python3N-base'.


Olaf

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]