Zbigniew Jędrzejewski-Szmek wrote:
> I think Suggests would be OK. Even Recommends seems like too much. You may
> be using clang++ to compile the code, or just accessing headers from
> doxygen, or maybe testing an alternate version of g++ from copr, i.e. with
> a different package name…
Suggests i
On Mon, Jan 31, 2022 at 08:57:45PM +0100, Kevin Kofler via devel wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
> > Well, that is the reverse of how we do things in general. If I want to
> > look for libraries using pkg-config, I install pkg-config. If I want
> > to look for libraries using 'gcc test.
* Robbie Harwood:
> Zbigniew Jędrzejewski-Szmek writes:
>
>> 1. pc(5) talks about "package", as if one would want to link to a
>>whole "package" instead one of the specific library files provided
>>by a package. Thankfully most .pc files only list one "-l" in Libs.
>>(Counterexamples:
Robbie Harwood wrote:
> k5crypto and com_err are internal libraries used across the different
> interfaces krb5 provides - they're not intended for external
> consumption, and upstream doesn't support their direct use by other
> applications.
Then they belong in Libs.private, not Libs.
> So you'r
Zbigniew Jędrzejewski-Szmek wrote:
> Well, that is the reverse of how we do things in general. If I want to
> look for libraries using pkg-config, I install pkg-config. If I want
> to look for libraries using 'gcc test.c -lfoo', then I install gcc.
>
> What we have now is like saying that .h files
On Mon, Jan 31, 2022 at 03:39:20PM +0100, Vít Ondruch wrote:
>
> Dne 31. 01. 22 v 14:09 Zbigniew Jędrzejewski-Szmek napsal(a):
> >Hi,
> >
> >various .pc files that we ship contain a lot of stuff in the Libs and
> >Libs.private field don't make much sense to me. I started looking at
> >the document
On Mon, Jan 31, 2022 at 05:20:39PM +0100, Kevin Kofler via devel wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
> > 3. We autogenerate a dependency on /usr/bin/pkg-config for -devel.
> > Logic is reversed here: the -devel package **provides** something
> > that it consumed by pkg-config. Dependencies
Zbigniew Jędrzejewski-Szmek writes:
> 1. pc(5) talks about "package", as if one would want to link to a
>whole "package" instead one of the specific library files provided
>by a package. Thankfully most .pc files only list one "-l" in Libs.
>(Counterexamples: tbbmalloc_proxy.pc says '
Zbigniew Jędrzejewski-Szmek wrote:
> 3. We autogenerate a dependency on /usr/bin/pkg-config for -devel.
> Logic is reversed here: the -devel package **provides** something
> that it consumed by pkg-config. Dependencies are from a consumer to
> the providing entity.
The idea there is that packages
Dne 31. 01. 22 v 14:09 Zbigniew Jędrzejewski-Szmek napsal(a):
Hi,
various .pc files that we ship contain a lot of stuff in the Libs and
Libs.private field don't make much sense to me. I started looking at
the documentation, and the documentation is very scarce, and what is
there doesn't seem to
Hi,
various .pc files that we ship contain a lot of stuff in the Libs and
Libs.private field don't make much sense to me. I started looking at
the documentation, and the documentation is very scarce, and what is
there doesn't seem to have been thought out at all. I'm writing my
observations and qu
11 matches
Mail list logo
