On Wed 2014-09-03 17:30:30 -0400, Daniel Kahn Gillmor wrote: > On 09/03/2014 04:25 PM, Helmut Grohne wrote: >> One thing that libgpg-error can do nonetheless is to move >> /usr/include/gpg-error.h to /usr/include/<triplet>/gpg-error.h. This >> avoids accidental inclusion of a wrong-architecture header. Refer to >> <20140829095214.gv19...@stoneboat.aleph1.co.uk> section 3.4 for details >> or ask me. >> >> In any case, turning libgpg-error-dev M-A:same should be a goal (and >> arguably this is the current meaning of the bug being discussed). For >> this reason alone, I argue that it should be kept open (and possibly >> retitled to "make libgpg-error-dev Multi-Arch:same"). > > Colin, does this sound reasonable to you?
I did some reading about what i think the goal is here: https://wiki.ubuntu.com/MultiarchCross Already, the .so and .a files present in libgpg-error-dev are at an arch-specific path. we would need to move /usr/include/gpg-error.h to /usr/include/$ARCH/gpg-error.h (since that file varies by architecture). Thus far, no problems. But the last remaining piece of doing this work is to deal with /usr/bin/gpg-error-config, which differs by architecture. The first recommendation here: https://wiki.ubuntu.com/MultiarchCross#Executables_in_-dev_packages is to help upstream switch to pkg-config, which Werner has explicitly stated he has no interest in doing, so that's out. All of the recommendations seem pretty problematic, actually, in terms of forcing an archive transition -- we'd require our downstream dependencies to change how they invoke gpg-error-config. One other approach, i suppose, is to modify gpg-error-config itself somehow to be able to invoke it with a different triplet (but have it default to something sane?) I'm really not sure what the best way to approach this is, but i'm open to specific suggestions. --dkg
pgpJPdN0WHgW2.pgp
Description: PGP signature
