Re: Mix of dynamic and static libraries

On Wed, Nov 22, 2000 at 05:40:48PM -0500, Joe Drew wrote: > I maintain distributed-net, which is created from multiple architectures > of upstream binary-only files. The problem is, I also need to depend on > another package, so on certain architectures (ie i386) ${shlibs:Depends} > is empty, and o

Re: Mix of dynamic and static libraries

On Wed, Nov 22, 2000 at 05:40:48PM -0500, Joe Drew wrote: > I maintain distributed-net, which is created from multiple architectures > of upstream binary-only files. The problem is, I also need to depend on > another package, so on certain architectures (ie i386) ${shlibs:Depends} > is empty, and

Mix of dynamic and static libraries

I maintain distributed-net, which is created from multiple architectures of upstream binary-only files. The problem is, I also need to depend on another package, so on certain architectures (ie i386) ${shlibs:Depends} is empty, and on others it has something in it. The problem arises when I add ano

Mix of dynamic and static libraries

I maintain distributed-net, which is created from multiple architectures of upstream binary-only files. The problem is, I also need to depend on another package, so on certain architectures (ie i386) ${shlibs:Depends} is empty, and on others it has something in it. The problem arises when I add an