guillem at debian.org
Sun Apr 10 22:34:38 PDT 2011
On Fri, 2011-04-01 at 16:41:57 -0500, Donnie Berkholz wrote:
> On 17:04 Fri 01 Apr , Joseph Tate wrote:
> > Conary has some really nifty tools for detecting dependencies. Some
> > of it runs on source code, like Python deps. And some runs on
> > compiled code, like for shared object dependencies, etc. I only know
> > about it as a user/packager though.
> Compiled code is easy. =)
Well, I'd reword that to “shared object dependencies are easy”.
Compiled code can have additional dependencies which might be optional
or required depending if it will gracefully fallback or degrade which
can be tricky to detect and which are not needed at build time, from
the top of my head those could be:
* Programs being execve()ed.
* Data files.
* Unix sockets, named pipes.
* System V/POSIX message queues, shared memory and semaphores.
* D-BUS (or other IPC system) interfaces.
More information about the Distributions