[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#752397: javahelper doesn't add libswt-cairo-gtk-3-jni when {java:Depends} is specified

On 2014-06-24 10:00, Pirate Praveen wrote:
> [adding debian-java list]
> On Tuesday 24 June 2014 10:14 AM, Niels Thykier wrote:
>> On 2014-06-23 14:14, Praveen Arimbrathodiyil wrote:
>>> package: javahelper, libswt-gtk-3-java
>>> severity: important
>>> [...]
>> Hi,
>> Does the JAR files in gnukhata use Class-Path?  If not, javahelper will
>> not be able to help you with dependencies automatically.  If it uses
>> Maven, you might have luck with the Maven helpers and if it uses OSGi,
>> then I believe you currently must do it manually.
> I think the issue is libswt-gtk-3-java missing the dependency, as java
> helper finds this dependency correctly.
> Hoping someone in debian-java can give a better insight.
>> ~Niels

True; I overlooked the fact that it was the swt-java -> swt-jni
dependency.  That said, javahelper never supported those!  Those are
from the same source and usually the Java package needs a very strict
dependency on the JNI dependency.

*In the particular case* - SWT is a bit special here, because it builds
a mandatory JNI (libswt-gtk-3-jni) and several "optional" extensions
(e.g. libswt-cairo-gtk-3-jni).  I suspect that gnukhata need to declare
a dependency on libswt-cairo-gtk-3-jni if it needs that particular
 * Admittedly, libswt-gtk-3-java could do with a Suggests/Recommends on
   its "optional" JNI packages.


Reply to: