Re: Debian 1.2 and .shlibs?
Dale Scheetz <email@example.com> wrote:
>Follow the directions in the dpkg programmers' manual for
>putting the shared library in its package, and make sure you include a
>shlibs control area file with details of the dependencies for
>packages which use the library.
>However there are no further details in the programmer's manual asside
>from the section you quoted, which is mostly about shared library
>dependencies and not about the file under discussion.
>The question remains:
>Do we satisfy the needs of other developers and package installers by
>placing a file named shlibs in the debian directory of the source tree? (I
>assume that is what is meant by "control area")
Yes and no - the control area is the DEBIAN subdirectory.
>I only have /etc/dpkg/shlibs.default on my system. I can only assume that
>if dpkg finds an shlibs file in the header section of a package that it
>updates this file with the contents.
No. As I understand this, what happens is dpkg-shlibdeps looks at the output
from ldd, and investigates the <package>.shlibs file in dpkg's info directory
(the <package>.shlibs file being, say, libelf0.shlibs - ie, the dependancy
information for libelf in this case.) If it finds appropriate information,
it generates the dependancy information.
The idea is that, once all shared libraries have this information,
/etc/dpkg/shlibs.default can be done away with. It means that dependancies
on shared libraries are taken care of automatically, reducing the need to
change control files when libraries are updated, etc.
Does this help? (I wrestled with this recently when putting together
libelf0_something-or-other-3... and now I'm told that 0.6.something is
available. Oops. :-)
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com