Hello everyone, I am currently beginning packaging aparapi, which is a Java API to execute Java code on a GPU. In Debian Med, we need it as dependency of the dependency apfloat of SnpEff.
This package relies on a JNI (native code) package which the same upstream develops as aparapi-native. Yet aparapi and aparapi-native are somehow interleaved, as aparapi depends on aparapi-native *and* aparapi-native needs a small number of source files of aparapi to build. I understand upstream uses symlinks to solve this locally on their computers. Having in mind Debian packaging, what would in your opinion be the best solution for us? We could: - build a package with multiple tarballs, which would provide both the JNI and Java binary packages; - use debian/missing-sources to add the few files that are needed by the JNI part and be able to build the two packages one after the other; - another solution? Thanks a lot for your attention, Best regards, Pierre
