On Mon, Dec 12, 2016 at 10:10:57AM -0700, Sean Whitton wrote: > > dpkg-shlibdeps automatically generates Depends on library packages > > corresponding to any libraries pulled in by the linker for the binaries > > in a package. However, library -dev packages still have to manually > > specify Depends on -dev packages that they require. In many cases, we > > could infer this information from pkg-config dependencies: if a library > > -dev package ships a pkg-config file, and that file includes Requires > > pointing to other pkg-config files, we could infer Depends on the > > packages shipping those other pkg-config files. > > > > I'd like to build some tools (possibly including a dh_pkgconfig) to do > > this automatically; those tools could generate a pkgconfig:Depends > > substvar for use in debian/control. Before starting on those tools, I'd > > like to get some feedback on this idea. > > I take it that you want to put the automatically detected dependencies > in the Build-Depends field? No, it's for Depends. If you additionally need a libb-dev when you are linking to liba, liba-dev would have Depends: libb-dev.
-- WBR, wRAR
signature.asc
Description: PGP signature
