using pkg-config for dynamic release packaging
Enrico Weigelt
weigelt at metux.de
Mon Aug 16 09:21:43 PDT 2010
* Tollef Fog Heen <tfheen at err.no> schrieb:
> Build dependencies are not run-time dependencies. I assume there's a
> hook late in the build process that looks at any installed .pc files and
> dumps the Requires information from those, which is then translated into
> actual package dependencies by something that knows that
>
> Requires: foo >= 1
>
> means it must find the package containing foo.pc and add that as a
> dependency.
Well, that only doesn't give a precise description. It requires more
deep analysis. For examples, binaries have to be examined for which
libraries they're linked against. But that yet doesn't tell
everything, eg. files that get loaded at runtime.
In the end there's no _reliable_ automatic way to do it, unless
we have some precise declaration coming from the package itself.
I'm currently working on an file classifier and dependency detector,
for use in package management and QM, but this is damned to be
imcomplete simply due lack of information.
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt at metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
More information about the pkg-config
mailing list