Re: Packaging a library that requires cross-compiled code
On 9/27/07, Daniel Jacobowitz <email@example.com> wrote:
> I think this is the way to go unless you get some concrete objections.
> There is certainly precedent - see for instance the ia32-libs /
> amd64-libs packages (which are frowned upon for whole different
[replying here, but this is a more general reply to the whole thread]
Thanks for the thoughts on this, I've decided to go with the above for
the time being, with the following addendums.
The upstream release (which I also author, but besides the point) also
bundles the binary driver, due to the difficulty of building it
directly. Given that I doubt this driver will ever change again now
that it works, that the source code is provided, and that the driver
is an internal implementation detail and not a pivotal component of
the software, it seems like the thing to do.
I also have a Debian package almost working now (lintian still has a
few complaints, and I need to file an ITP iiuc), which uses the
upstream binary driver to build the debian package. I don't know
whether this now qualifies as main or contrib, given that the binary
is provided by upstream, and therefore no special software is required
to actually build the package.