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

Re: building Debian source packages



-----BEGIN PGP SIGNED MESSAGE-----

On Wed, 7 Apr 1999 shaleh@clifford.livenet.net wrote:

> The problem is that both use the same lib name (lesstif has to so it can be
> a replacement for Motif).  The only safe solution is to remove any lesstif
> pacakges you have, then build a motif package.  Then apps can depends
> correctly.

I don't have lesstif installed at all...
# dpkg -S libXm.so
motif-runtime: /usr/X11R6/lib/libXm.so.1
motif-runtime: /usr/X11R6/lib/libXm.so.1.2
motif-runtime: /usr/X11R6/lib/libXm.so

motif-runtime is the debian package I built that includes the Motif
shared libs.  But when I build a local copy of, for example, Plan, the
resulting package depends on lesstifg.  For example, <plan>/debian/control
has the following line:
Depends: ${shlibs:Depends}

However, <plan>/debian/tmp/DEBIAN/control contains the following line:
Depends: lesstifg (>= 19980310), libc6, xlib6g (>= 3.3-5)

How does dpkg-shlibdeps (or whatever comes up with the dependencies)
decide that plan depends on lesstif when it is linked against a library
that is part of my Motif package???  An ldd of the plan executable shows
that it is dynamically linked against the library that is installed by my
motif-runtime package, as it should be.

> 
> Of course the other answer is to support the lesstif people.
> 

Unfortunately, I can't do that at this point.  I use a Motif C++
application framework called ViewKit (www.viewkit.com) that depends on
some internal (undocumented) Motif functions.  Lesstif really can't ever
support this, since in order to know about these functions, they would
have to have seen the Motif source code.  Seeing the source code to a
commercial program puts you in a bad legal position when you're trying to
code a free clone of the same program....

noah

  PGP public key available at
  http://lynx.dac.neu.edu/home/httpd/n/nmeyerha/mail.html
  or by 'finger -l frodo@ccs.neu.edu'

  This message was composed in a 100% Microsoft free environment.



-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNwuZq4dCcpBjGWoFAQHzUQQAkjiLUesjBuehYTYdJtUu8OrJ6cePm1iY
4IoQCdsqxI5gs3u5VEdTtP/cmdLpU75HzaXst9mCHCLvTNMD3Dpvmcba/aF9sgdy
ZJ/bmD6e4Np432R5jI2DiwGstUvIwAozjLvb+dyQ5Lgw53qbwYLLWbPsxhw4kNI0
rLyqbvrFRRo=
=ezXP
-----END PGP SIGNATURE-----


Reply to: