Le jeu. 18 juil. 2019 à 17:12, Philip Kovacs via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> a écrit : > > > It does not matter if the config process uses pkgconfig or not. > > Depending on the package name is not a way to state you're not using > > pkgconfig, it's a way to get broken builds when the package you depend > > on gets restructured. > > Then the docs should be strengthened to state the case from the perspective of the provider > of the .pc and not the consumer of it: > > Current: > > "Fedora packages which use pkg-config to build against a library (e.g. 'foo') on which they depend, > SHOULD express their build dependency correctly as pkgconfig(foo)." > > becomes: > > "Build dependencies on Fedora packages which provide pkg-config files SHOULD be expressed > as pkgconfig(foo) and not foo-devel, whether the dependent package uses pkg-config or not." This is true for the fast majority of cases. Specially where there is only one provider of pkgconfig(foo). But sometime there is a need for a compat library and then I don't know if my package may uses the main library of the compat one. pkgconfig(foo) will pick one or the other, but using the package name is more deterministic to me. -- - Nicolas (kwizart) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx