tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: question

On Mon, Apr 15, 2013 at 01:48:55AM +0300, Aleksey Cheusov wrote:
> Suppose we have package A that provides,
> and package B that provides
> Package A depends on B, and is unconditionally linked with
> We also have packages C_1..C_n that depend on A and its
> binaries are linked with (and _possibly_ directly with
> Does this mean that it is always better to add
>   .include "B/"
> to "A/" and remove it from C_i/Makefile ?
> If not, we'll have the same
>   .include "B/"
> in multiple places or build failures if C_i need


If A links against B or uses headers from B in its header files, A's must include B's

Independent of that:
If C uses B directly, it must include its

So a mix of your answers, I think :)

> Real example:
> A  -- x11/libdrm (
> B  -- sysutils/libpciaccess

So what is to be changed here, if anything?

Home | Main Index | Thread Index | Old Index