postfs1; I see what you`re doing, but I`m not sure how it applies to web.
I suppose if I download an Ubuntu CD and use "find" to generate a list...
A list search is much faster than extracting Deb. files from a CD.

# The perfect thing would be a list of: files and libs. => package.

# I`m really surprised ( and disappointed...) Ubuntu doesn`t have this.
It seems that a file manifest list like this would be part of the Ubuntu CD.

So ldd shows missing libs. and the list shows what packages they`re in.
Then awk could find the package in one command.
Then it`s easy to find and download the packages from a Ubuntu mirror.

I have several Ubuntu files of lists, but none that are: file => package.
One I have is package descriptions, but no package contense is listed,
and it doesn`t contain all of the available packages.

I think you need to be looking elsewhere for the info. rather than using ldd. When you download and install some deb/ubuntu package, it contains a file called 'control' which will list the other packages needed by the package.

I guess there is a way to do what you want, but the info you get may not be accurate -you may find the wrong version before finding the right one. Only the control file will tell you all the info you need.

http://packages.ubuntu.com/en/lucid/ gives such a file:
http://packages.ubuntu.com/en/lucid/allpackages?format=txt.gz

https://launchpad.net/ubuntu/lucid/i386/+builds?build_text=&build_state=built gives such a files:
https://launchpad.net/ubuntu/+source/portmidi/1:200-0ubuntu1.10.04.1/+build/4207230/+files/buildlog_ubuntu-lucid-i386.portmidi_1%3A200-0ubuntu1.10.04.1_BUILDING.txt.gz

control file content:
Version: 2.68-1ubuntu2
Architecture: all
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Installed-Size: 1858
Depends: perl (>> 5.005), m4 (>= 1.4.13), debianutils (>= 1.
Recommends: automake | automaken
Suggests: autoconf2.13, autoconf-archive, gnu-standards, autoconf-doc, libtool, gettext
Conflicts: autoconf2.13 (<< 2.13-47), gettext (<< 0.10.39), pkg-config (<< 0.25-1.1)
Section: devel
Priority: optional
Multi-Arch: foreign
Homepage: http://www.gnu.org/software/autoconf
Description: automatic configure script builder
The standard for FSF source packages. This is only useful if you
write your own programs or if you extensively modify other people's
programs.
.
For an extensive library of additional Autoconf macros, install the
`autoconf-archive' package.
.
The Debian project regards the full documentation for autoconf to be
non-free, so it is not included in Debian. Nevertheless, the
non-free distribution that accompanies Debian includes the manual in
its `autoconf-doc' package.
.
This version of autoconf is not compatible with scripts meant for
Autoconf 2.13 or earlier. If you need support for such scripts,
you must also install the autoconf2.13 package.
Original-Maintainer: Ben Pfaff <pfaffben@debian.org>

You are using dpkg, so it should find the right package with just the name -if you have the repos configured correctly. If you are installing packages from contribs repo, then that will have to in the repos configuration. If a package needs updates of normal packages, then the updates should be in the same repo as the original extra/updated program.

Are we having fun yet, working with dependency-management? If not, try coming up with a better system than debian/dpkg. The only more-complete system would be what nix OS is doing -by providing multi-version capability for everything. A real nightmare for the devs!

Sorry if I'm being hard -it's been below freezing for days here and I am getting grumpy and ornery...

amigo; No need to apologize, I remember how cold it was in Pennsylvania. And I remember how quickly you get use to the warmth here in the desert.
Tuesday night it actually got down to 27F ( ~ -2C ), the lowest it`s been. Any desert has greater temperature extremes than moist areas.
When the sun goes down the temp. can drop 10F to 20F in an hour.

If dpkg requires lots of configuration, then it`s no better than parsing web pages. Providing mirror URLs is easy, but I`m still not sure about using it.

About 2 to 3 web pages need to be parsed for the links to the dep. page. Then loop to check the dep. list for installed libs. or if it`s on a local drive.

I have an option to warehouse libs. in the AppPkg build dir. to keep from downloading libs. repeatedly in making AppPkgs.
At this point why not include it in the lib. path ( ld.so.conf ) so eventually no more downloading of libs. needs to be done.
That is, until the next major upgrade when you dump the whole mess and start downloading the next batch of newer libs.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum