On Sun, Feb 17, 2013 at 09:46:52PM +0100, Romain Francoise wrote: > Helmut Grohne <hel...@subdivi.de> writes: > > Multi-Arch: foreign > I can do that, but can you describe your use case? In which situations > would a tcpdump reverse dep be of a different architecture? They tend to > be very high-level stuff.
Mixing architectures is not yet that common, but I expect it to become common. One reason for this is the x32 architecture which promises a slight performance boost at the cost of a 4GB memory (per process) cap on an x86_64 host. I guess that users would install a regular amd64 system and swap out some performance critical software with x32 binaries. tcpdump is also a build dependency of tcprelay. In order to make cross-compilation of the archive possible (some people try to do that, but the idea is not universally accepted), tcpdump would need this header as well. In practise we do not yet know all the use cases. People will make wonderful things with it. That said I do not thing this header update should target wheezy. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
