Stephen Zander <[EMAIL PROTECTED]> writes:

> What is the thinking behind always requiring libfoo-dev to depend on
> libbar-dev when libfoo depends on libbar?  I understand the need when
> /usr/include/foo.h contains
> 
>   #include <bar.h>
> 
> but if libfoo opaquely wraps libbar, why have libfoo-dev depend on
> libbar-dev?

Do you have a case where theres no #include <bar.h>? Then you would
just build-depend on libbar-dev.

If it works 100% without there is no need to depend.

MfG
        Goswin


Reply via email to