On Tue, Apr 30, 2019 at 2:34 AM Vít Ondruch <vondruch(a)redhat.com> wrote:
Dne 28. 04. 19 v 22:55 Zbigniew Jędrzejewski-Szmek napsal(a):
> Hi everyone,
>
> currently, we autogenerate a dependency on pkg-config for all rpms
> that ship a .pc file. "dnf repoquery --whatrequires /usr/bin/pkg-config"
> returns 4632 entries on my laptop.
>
> This has always felt backward to me: those packages *provide* something
> that is used by pkg-config, they don't *require* pkg-config for anything.
> As an analogy, packages with headers are read by a C compiler, but
> we don't make them require gcc, and if a package ships an .so file, we
> don't add a dependency on the linker to it. Instead, anything which wants
> to consume .pc files should simply depend on the tools that consume those
> files (pkg-config, pkgconf, or a custom re-implementation).
I don't think that this is completely wrong. However that dependency
should not be "Requires" but probably "Suggests". Not that we can
really
benefit from "Suggests".
If it is made into a weak dependency (like Recommends or Suggests),
then it doesn't show up in build roots, since we don't have weak
dependencies on there. If it is Suggests, then _no one_ gets it, not
even regular users...
--
真実はいつも一つ!/ Always, there's only one truth!