Re: Project idea: port GKL to non-x86

[Steffen Möller <steffen_moeller@gmx.de>]

On 18.11.20 10:35, Michael R. Crusoe wrote:
>
>
> On Wed, 18 Nov 2020 at 10:32, Andreas Tille <andreas@an3as.eu
> <mailto:andreas@an3as.eu>> wrote:
>
>     Hi Michael,
>
>     On Wed, Nov 18, 2020 at 12:00:29AM +0100, Michael Crusoe wrote:
>     > With https://salsa.debian.org/java-team/gkl/-/merge_requests/3
>     <https://salsa.debian.org/java-team/gkl/-/merge_requests/3> I am
>     able to
>     > build a GKL package that runs on non-amd64 (though probably at a
>     huge speed
>     > sacrifice)
>     >
>     > Using the resulting libgkl-java package and
>     >
>     https://salsa.debian.org/med-team/picard-tools/-/commit/a6e95fb137e4293491b84e04b780bd6ebd5cfe34
>     <https://salsa.debian.org/med-team/picard-tools/-/commit/a6e95fb137e4293491b84e04b780bd6ebd5cfe34>
>     > I am able to build and run Picards tools on arm64
>
>     Cool.  Should I upload gkl (after some routine-update)?
>
>
> Already done :-)
>  
>
>     I also wonder why that package is in java-team if only Debian Med
>     members are working on it and its relevant for Debian Med.
>
>
> I don't know!

The idea typically is that if there is something happening on the Java
front with many reverse dependencies then this can be dealt with. For
some packages there should be dual-memberships.

Best,

Steffen