Package: plib1.8.4c2
Version: 1.8.4-8
Severity: serious
Justification: Policy 10.2

If you really insist on building shared libraries for plib, they should be
done properly. Ideally, it should be possible to build against it without
having to tweak any makefiles to compensate for unexpected inter-library
dependencies. After all, authors will expect that only pieces of an .a file
gets pulled in, but if you link against a .so, you end up linking the whole
thing, including parts you don't need or want, and that may depend on other
libraries.

Currently, makefiles typically do need to be tweaked, because the plib shared
libraries are currently not linked against whatever they're depending on.

And that last thing is a policy violation, as, starting with policy version
3.6.0, section 10.2 has been saying:

"shared libraries must be linked against all libraries that they use symbols
from in the same way that binaries are."

For example, libplibssg.so seems to use symbols from libplibsg.so,
libplibul.so, and libGL.so, but isn't linked against them.

Now, my own simgear package currently suffers from similar problems, but
I've been working on a build system to fix it, it will be in simgear 1.0.0-3.
If you don't want to invent your own system, you could probably look at and
adapt my system if you like. My simgear upload is probably stuck in NEW
right now (I renamed the package), but I also put it up at
http://people.debian.org/~ovek/ just in case.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages plib1.8.4c2 depends on:
ii  freeglut3                    2.4.0-6     OpenGL Utility Toolkit
ii  libgl1-mesa-glx [libgl1]     7.0.3~rc2-1 A free implementation of the OpenG

plib1.8.4c2 recommends no packages.

-- no debconf information





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to