Hello everyone,
I need your advice on a packaging issue I am meeting right now.
I am in the course of packaging gatk-bwamem-jni [0], providing a native
interface which allows one to use bwa (Debian packaged [1]) from Java
code. Fine.
But the upstream of gatk-bwamem-jni relies on a version of
On 3/13/22 8:05 PM, Pierre Gruet wrote:
What should I do? My proposal would be to design a multiple upstream tarball for
gatk-bwamem-jni: original one + the sources at the tip of the Apache2 branch of
bwa.> It would build a libbwa.a lib which would not be installed in /usr/lib,
but in a privat
Hi Nilesh,
Thanks for the quick answer. Your advice is much appreciated, as always.
Le 13/03/2022 à 15:46, Nilesh Patra a écrit :
On 3/13/22 8:05 PM, Pierre Gruet wrote:
What should I do? My proposal would be to design a multiple upstream
tarball for gatk-bwamem-jni: original one + the sources
Hi Pierre,
On 2022-03-13 16:35, Pierre Gruet wrote:
> My proposal would be to design a multiple upstream tarball for
> gatk-bwamem-jni: original one + the sources at the tip of the Apache2
> branch of bwa. It would build a libbwa.a lib which would not be
> installed in /usr/lib, but in a private d
4 matches
Mail list logo