Re: Can we stop revbumping the world please?

[Thomas Klausner <wiz%gatalith.at@localhost>]

On Wed, Nov 20, 2024 at 11:25:22AM +0100, Dr. Thomas Orgis wrote:
> > or if a library uses the dependency's
> > library.
> 
> But I don't see that. If package C needs libb from package B and links
> to it in its build, and is not interested in libb also depending
> (linking dynamically) to liba from package A, it should not be made to
> depend on A.

There are two kinds of library dependencies. You can see the
difference easily in pkg-config files:

Requires:

and

Requires.private:

Requires means that the main library uses the other library's
interface in a way that users of the main library can access it or
need to be aware of it, so the other library also needs to be linked
in.

Requires.private means that the main library uses the other library's
interface in a hidden way, as a kind of implementation detail, but
users of the main library don't need to know and don't need to link
against the other library (except, I think, when linking statically).

buildlink3.mk must include the buildlink3.mk files for the first
type, but not the second.
 Thomas