Subject: shlibdeps

From: Michael Meskes <[email-masked]>
Date: Tue, 3 Sep 1996 10:14:54 +0200 (MET DST)

Are we supposed to use dpkg-shlibdeps for all dependecies upon shared libs?
Or is it just for the three (or so) installed in /etc/dpkg/shlibs.default?

So what do I do with xpm for instance?

Michael

-- 
Michael Meskes                   |    _____ ________ __  ____
[email-masked] |   / ___// ____/ // / / __ \___  __________
[email-masked]                  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[email-masked]                |  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian GNU/Linux!            | /____/_/      /_/  /____/\___/_/  /____/

---

From: [email-masked] (Owen Dunn)
Date: Tue, 3 Sep 1996 22:23:25 +0100

>Are we supposed to use dpkg-shlibdeps for all dependecies upon shared libs?

I believe so, yes.

>Or is it just for the three (or so) installed in /etc/dpkg/shlibs.default?

Ian will correct me if I'm wrong, but I think (under the New Scheme of
Things) packages which provide shared libraries should have a
debian/shlibs file detailing the appropriate dependency information.

Until all packages which provide shared libraries are converted to
provide this file, we could:

(1) Have all the shlibs information in /etc/dpkg/shlibs.default. (This
happened with the X libraries.)

or (2) Temporarily put the appropriate information in
debian/shlibs.local in the package with the dependency on the shared
library.

IMO neither of these is wonderful; thoughts?

(S)