-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2019-07-19 7:49 a.m., Rex Dieter wrote:
> Remi Collet wrote: > >> Le 18/07/2019 à 18:26, Nicolas Chauvet a écrit :
> "Build
dependencies on Fedora packages which provide pkg-config files
SHOULD be expressed as pkgconfig(foo) and n
Remi Collet wrote:
> Le 18/07/2019 à 18:26, Nicolas Chauvet a écrit :
>>> "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
On Fri, Jul 19, 2019 at 7:14 AM Nicolas Chauvet wrote:
>
> Le ven. 19 juil. 2019 à 10:33, Nicolas Mailhot via devel
> a écrit :
> >
> > Le vendredi 19 juillet 2019 à 08:48 +0200, Remi Collet a écrit :
> > > Le 18/07/2019 à 18:26, Nicolas Chauvet a écrit :
> > > > > "Build dependencies on Fedora p
Le ven. 19 juil. 2019 à 10:33, Nicolas Mailhot via devel
a écrit :
>
> Le vendredi 19 juillet 2019 à 08:48 +0200, Remi Collet a écrit :
> > Le 18/07/2019 à 18:26, Nicolas Chauvet a écrit :
> > > > "Build dependencies on Fedora packages which provide pkg-config
> > > > files SHOULD be expressed
> >
Le vendredi 19 juillet 2019 à 08:48 +0200, Remi Collet a écrit :
> Le 18/07/2019 à 18:26, Nicolas Chauvet a écrit :
> > > "Build dependencies on Fedora packages which provide pkg-config
> > > files SHOULD be expressed
> > > as pkgconfig(foo) and not foo-devel, whether the dependent
> > > package u
Le 18/07/2019 à 18:26, Nicolas Chauvet a écrit :
>> "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. Spe
Nicolas Mailhot via devel wrote:
> 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.
On the other hand, there are also cases where pkgconfig(foo) can break:
* if compatibility librar
Le jeu. 18 juil. 2019 à 17:12, Philip Kovacs via devel
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 res
On Thu, Jul 18, 2019 at 10:26 AM Philip Kovacs via devel
wrote:
>
> A "necessary and sufficient" question on the use of .pc files supplied by
> library providers.
>
> 1. Package foo-devel installs a pkgconfig .pc file as a convenience to
> developers.
> 2. Package bar requires headers and librar
> 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
As stated in
https://docs.fedoraproject.org/en-US/packaging-guidelines/PkgConfigBuildRequires/
pkgconfig(foo) is a more reliable marker of what ships the devel files,
than the package name.
It does not matter if the config process uses pkgconfig or not.
Depending on the package name is not
A "necessary and sufficient" question on the use of .pc files supplied by
library providers.
1. Package foo-devel installs a pkgconfig .pc file as a convenience to
developers.
2. Package bar requires headers and libraries provided by foo and is both a
build and runtime dependency of foo.3. Pa
12 matches
Mail list logo
