gcmd-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gcmd-dev] checking missing dependencies (script)


From: Magnus Stålnacke
Subject: Re: [gcmd-dev] checking missing dependencies (script)
Date: Tue, 21 Nov 2006 17:08:49 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20051003

Micha wrote:

~$ grep libX11.so.6 /var/log/packages/*.* | sed 's/.*es\///g'
32x11-6.8.2-x86_64-1:usr/lib/libX11.so.6.2
32x11-6.9.0-x86_64-2:usr/lib/libX11.so.6.2
x11-6.8.2-x86_64-8:usr/lib64/libX11.so.6.2


I see filenames are not lowererd as in debian.

No slackware package changes any filename, they have the
names their authors decided them to have.


Woukd it work to have a real 64 gcmd ?

Yes, my GCMD is compiled as 64-bit.


But if the question is:
What package contain libfoo.what.ever?


Exactly, But there's a step before: What libs are needed to compile ?

If you get an answer to that, you need a list that can
answer what package those libs are in.


<q>
mi: apt-cache show gnome-commander

Package: gnome-commander
Priority: optional
Section: gnome
Installed-Size: 2424
Maintainer: Michael Vogt <address@hidden>
Architecture: i386
Version: 1.2.0-3.2
Depends:

No no, the other way around.

That lists what the package maintainer says are dependencies.
What i mean is "in what package can i find a ceartain file?"
not "what other package do this need?"
Do Debian have such file? (any file, not only libs)

I mean a list of every file contained in every package,
a file list, not only a package list.

Like this:
http://ftp.scarlet.be/pub/slamd64/slamd64-11.0/slackware/MANIFEST.bz2

If i miss a lib, i just look in that file to see what
package i have to install. If the missing lib is not
listed in that file, then the lib (or file) is not part
of Slamd64 (or Slackware) and it have to be found elseware.

This is dependency resolving turned upside down compared
to other distros. Insted of listing, in the package, what
other packages it may depend on, it starts from what libs the
program in the package really needs, and then looks up in
what package those libs can be found. The tool SWARET works
like this.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]