Hi Stefano & python-debian maintainers,
Looking at the patches to support :any relationships in python-debian, I think
I have to agree that adding :any and :native at the same time makes sense.
https://wiki.ubuntu.com/MultiarchCross
The present set of patches for :any adds a key 'foreign-arch' to the
dictionary that is True if :any has been specified. Does it make sense to add
yet another key for :native? Or would setting a generic key that contains
either 'native', 'any' or ''/None (for the unqualified case) make more sense?
For reference Dpkg::Deps.pm does this with the key 'archqual' and I'm quite
tempted to say that sticking close to what Dpkg does has advantages here.
http://sources.debian.net/src/dpkg/1.17.9/scripts/Dpkg/Deps.pm?hl=682#L576
thoughts?
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
