[Multiarch-devel] cross-architecture conflicts or equivalent for libc packages
Jakub Wilk
jwilk at debian.org
Mon May 19 12:01:15 UTC 2014
* Aurelien Jarno <aurelien at aurel32.net>, 2014-05-19, 13:28:
>>>i386 /lib/ld-linux.so.2
>>
>>Provides: lib-ld-linux-so-2
>>Conflicts: lib-ld-linux-so-2
>>Replaces: lib-ld-linux-so-2
>
>So following your way, it would be exactly the same for libc6:sparc.
>
>libc6-i386 also provides /lib/ld-linux.so.2. It should be
>co-installable with libc6:i386, but libc6:sparc should not be
>co-installable with libc6:i386 or libc6-i386.
Oh, right. Couldn't the biarch packages die already? :)
If they can't, I suppose you can implement cross-architecture conflicts
with plain conflicts against virtual packages:
Package: libc6
Architecture: i386
Provides: libc6-on-i386
Conflicts: libc6-on-sparc, ...
Package: libc6-i386
Architecture: amd64
Conflicts: libc6-on-sparc, ...
Package: libc6
Architecture: sparc
Provides: libc6-on-sparc
Conflicts: libc6-on-i386, libc6-i386, ...
--
Jakub Wilk
More information about the Multiarch-devel
mailing list