|
From: Daniel M. <dm...@ne...> - 2006-08-30 15:00:17
|
On Wed, Aug 30, 2006 at 09:47:45AM +0200, Martin Costabel wrote:
> Jean-Fran?ois Mertens wrote:
> > On 30 Aug 2006, at 04:56, Koen van der Drift wrote:
> >
> >> Is there a command that shows which packages either depend or
> >> builddepend on another package (xorg and xorg-shlibs in this case) ?
> >
> > There might be a play with apt or fink rm -r if they have something
> > like a 'dry-run' option..
>
> They do, at least apt-get does:
>
> sudo apt-get remove xorg-shlibs --dry-run
>
> should do the trick. I don't think builddependencies would be important
> in the context of the original question. Or is there a reason why they
> could?
BuildDepends shouldn't matter, since all one cares about is runtime
linkages to the x11 shared libraries (otool -L results). That
technically means Depends:x11-shlibs. However, maintainers usually do
Depends:x11 instead ("What good is having a program linked against x11
if there's no x11 server available?" Don't answer...that's a debate
for another day). However, maintainers sometimes rely on the fact that
Depends is recursive, so if foo needs x11, one could have
foo:Depends:bar and bar:Depends:x11-shlibs but no explicit
foo:Depends:x11-shlibs.
OTOH, in order to link against x11-shlibs for runtime, one needs to
BuildDepends:x11-dev and BuildDepends is *not* recursive. Therefore,
any package that links against x11 libs *must* BuildDepends:x11-dev
even if it does not Depends:x11-shlibs itself. That might be the
necessary and sufficient property here. Note that for your
inconvenience, BuildDepends is not in the .deb nor anywhere else that
dpkg or apt can see it.
> []
> > The main drawback would be that dpkg-awk limits you to already built
> > pkgs...
>
> What is dpkg-awk? Again, in the context of this thread only installed
> packages are interesting anyway.
I disagree...could have built-against-xorg but not-presently-installed
packages in his .deb collection.
dan
--
Daniel Macks
dm...@ne...
http://www.netspace.org/~dmacks
|