* Joey Hess <[EMAIL PROTECTED]> [030617 19:30]: > Package: libfoo1 > Package64: lib64foo1 > Provides: libfoo1-$(architecture) > Architecture: any > Description: the foo library > The foo library for all your bar needs. > Description64: the 64 bit foo library > The foo library for all your 64 bit bar needs. > > Package: libfoo-dev > Package64: lib64foo-dev > Architecture: any > Depends: libfoo1-$(architecture) > Conflicts: libfoo-dev > Description: the foo library development files > Development files for the foo library. > Description64: the 64 bit foo library development files > Development files for the 64 bit foo library.
I have been following the thread and like what I see.
I have a small issue that I am not sure how to address.
On a 64 bit kernel with 32 bit binary emulation support, you can run
aything. However, when using a 32 bit kernel, one must have at least a
32 bit modutils. Running a 64 bit insmod, which I had the displeasure
of doing once, is disastrous on a 32 bit kernel.
There may be other instances where a package (ex: the i386 kernel) would
require another to provide a particular binary variant (ex: the i386
modutils).
Granted this is a small problem.
Bart.
--
WebSig: http://www.jukie.net/~bart/sig/
pgppSEx8U39s3.pgp
Description: PGP signature
