Aurelien Jarno <aurel...@aurel32.net> writes: > On Mon, Oct 12, 2009 at 01:05:18PM +0200, Guillem Jover wrote: > Another option is that all the Provides: part of type-handling is done > on dpkg. The current problem with the implementation: > - A rebuild of type-handling is needed each time a new architecture is > added to dpkg. > - Provides do not always work as an alternative. This require for > example type-handling to be installed on the build daemons > (technically it should be an Essential package for this to work). > > That's why I am not really for more usage of type-handling, which IMHO > should simply disappear.
This gets even worse with multiarch. Depending on the dpkg config (what archs to allow, and any multiarch config will break something) the type-handling will break down. Examples: amd64 + i386: amd64 has not-i386 and i386 has not-amd64. It is kind of strange that you are both i386 and not-i386 but that is multiarch for you. amd64 + kfreebsd-amd64: Now you have linux and not-linux. I already saw some nice confusing effects of this with ia32-apt-get and had to blacklist type-handling from the non-native archs. MfG Goswin -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org