On 04/12/12 02:48, Colin Watson wrote:
> Package: graphviz
> Version: 2.26.3-12
> Severity: wishlist
> Tags: patch
> User: [email protected]
> Usertags: cross
>
> graphviz is Architecture: any, but on a multiarch system it doesn't
> matter which architecture you get as long as you can execute its
> binaries. It's a build-dependency of 179 packages in unstable.
> Accordingly, it would be helpful to mark it Multi-Arch: foreign to avoid
> blocking cross-builds of those packages; that would allow cross-builds
> to use the version of graphviz for the architecture being built on,
> which is generally best for tools as opposed to libraries.
>
> * Mark graphviz Multi-Arch: foreign.
>
> diff -Nru graphviz-2.26.3/debian/control graphviz-2.26.3/debian/control
> --- graphviz-2.26.3/debian/control 2012-07-10 23:37:19.000000000 +0100
> +++ graphviz-2.26.3/debian/control 2012-12-04 02:44:20.000000000 +0000
> @@ -49,6 +49,7 @@
>
> Package: graphviz
> Architecture: any
> +Multi-Arch: foreign
> Depends: ${shlibs:Depends}, ${misc:Depends}
> Conflicts: gdtclft
> Recommends: ttf-liberation
>
> Thanks,
>
Hi Colin,
Apologies for not responding sooner, but I've been taking a bit of an
hiatus from graphviz while the freeze was in place.
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).
Cheers,
David.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
