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 on others it has something in it. The problem arises when
> I add another dependency: it either ends up to be
> Depends: logrotate,
> or Depends: ,logrotate
> both of which confuse dpkg-deb. Is there any way around this, seeing as
> it will be necessary to have ${shlibs:Depends} on certain architectures?
You can do the evil thing and regenerate debian/control from
another file in debian/rules, depending on what dpkg-architecture
-qDEB_BUILD_ARCH is.
There's probably another, smoother solution, which I can't think of right
now :)
--
Digital Electronic Being Intended for Assassination and Nullification
