Shared libs vs. plugins.

2001-04-26 Thread Daniel Kobras
Moi! In the process of packaging the sound editor glame, I noticed this small issue: Glame (and other packages like xmms for example) makes use of plugins that are dlopen()ed on demand at runtime. Those plugins are compiled and linked as shared libs, but obviously, one does not want to create a sh

Bug#93975: Make shared libs non-mandatory.

2001-04-14 Thread Daniel Kobras
On Sat, Apr 14, 2001 at 10:28:57AM -0700, Sean 'Shaleh' Perry wrote: > I maintain libnet this way, it only ships as a static lib. So I have a > libnet0-dev package. Someday I hope to have a shared version. My libmad > package used to only be static, but now I have both. > > Not really sure we n

Bug#93975: Make shared libs non-mandatory.

2001-04-14 Thread Daniel Kobras
Package: debian-policy Version: 3.5.2.0 Severity: wishlist Moi! I have prepared a package of libdv, a library to de- and encode digital video data, and noted that it violates current policy: The x86 version of the library contains optimized assembler routines that are not relocatable. Therefore,