On Tue, May 14, 2013 at 11:12:27PM +0100, David Claughton wrote: > Apologies for not responding sooner, but I've been taking a bit of an > hiatus from graphviz while the freeze was in place.
No problem. > Can I just clarify - is your suggestion of "Multi-Arch: foreign" > intended as a stop-gap pending the implementation of a full Multi-Arch > implementation of graphviz? The reason I ask, is because I have 2.28 > waiting in the wings on the git archive which has multi-arch implemented > (or nearly so, I just need to test the -dev package and then actually > mark the packages Multi-Arch: same). > > Would a Multi-Arch:same graphviz meet your needs? If so, I'll close > this bug with 2.28 when it's uploaded. (If not, I've badly > misunderstood something somewhere). I don't understand how graphviz itself could possibly be Multi-Arch: same. Things like libgraph4, sure, but you can't make a package that ships compiled code in /usr/bin/ M-A: same - builds on different architectures will inevitably clash - and it wouldn't really be very useful to try. M-A: same is normally for packages containing libraries and such, not for packages containing executables on $PATH. I certainly encourage you to make libraries M-A: same wherever possible, but it's orthogonal to this bug. Cheers, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
