* Package name : libaparapi-java Version : 2.0.0 Upstream Author : Gary Frost, Syncleus, Inc. * URL : http://aparapi.com/ * License : Apache-2.0 Programming Lang: Java Description : framework for executing native Java code on the GPU This framework converts Java bytecode to an OpenCL kernel dynamically at runtime, to allow Java code to be executed on a graphics card GPU. This allows developers to take profit from GPU architecture while writing Java programs. This package will be taken care of in Debian-med team, where it is needed as a dependency of apfloat, which is itself a dependency of SnpEff.
Hi I noticed you had a conversation sometime back here: https://github.com/aparapi/aparapi/issues/50 I wanted to mention that Aparapi is no longer maintained at the address you specified and all developers, including the founder, have moved onto the new repository which is now active and well funded here: https://git.qoto.org/aparapi/aparapi During that port back in 2016 the license was reviewed by a paid lawyer hired by the new foundation and the license was legally changed. As our lawyer had assured us the original additional verbiage in the license for the original release of Aparapi did not functionally change the license in any way, it simply allowed AMD to protect themselves against any liability should the software be misused. The original added verbiage basically amounted to "You can not break the law when you exercise your rights under this license", which is already implied with an MIT license but not explicitly stated. As such we were able to legally and effectively relicense the software under the apache license and the new software is licensed wholly under the Apache license with no additional restrictions of any kind. You are free to repackage and redistribute the license exactly as you would under the Apache license. Let me know if you have any questions.
Glad to hear it. If you have any questions at all reach out to me anytime. I've been the package maintainer for some time. While I am not the founder I handle most of the day to day coding and project management and am in close contact with the original founder who is still a contributor and active participant but not as active as myself these days. So I try to handle any of the day to day issues that come up. Always happy to answer any questions if you need anything.
I am changing the ITP bug to RFS because the wording of the license still precludes packaging. The blocking part is the last paragraph in ATTRIBUTIONS.md: it does not seem to be harming when considering packaging aparapi itself, but it would impose restrictions on other software that might be bundled with it. We will discuss it with upstream and consider packaging later. Pierre Gruet
(this is RFP and not RFS, sorry...) I am changing the ITP bug to RFP because the wording of the license still precludes packaging. The blocking part is the last paragraph in ATTRIBUTIONS.md: it does not seem to be harming when considering packaging aparapi itself, but it would impose restrictions on other software that might be bundled with it. We will discuss it with upstream and consider packaging later. Pierre Gruet