Bug#640354: libisfreetype-5.2-java: circular dependency with libisnativec-java
steffen_moeller at gmx.de
Mon Sep 5 20:59:36 UTC 2011
On 09/05/2011 10:42 PM, Bill Allombert wrote:
> On Sun, Sep 04, 2011 at 06:24:31PM +0200, Torsten Werner wrote:
>> On Sun, Sep 4, 2011 at 4:00 PM, Bill Allombert <ballombe at debian.org> wrote:
>>> There is a new circular dependency between libisfreetype-5.2-java and libisnativec-java:
>>> libisfreetype-5.2-java :Depends: libisnativec-java
>>> libisnativec-java :Depends: libisfreetype-5.2-java
>> what do you suggest as a solution?
> Well, I do not know why libisnativec-java would need libisfreetype-5.2-java,
> but generally in similar case, libisnativec-java is be split in two packages,
> one low-level needed by libisfreetype-5.2-java and one high-level that use
> libisfreetype-5.2-java. We would have:
> libisnativec-java-highlvl Depends: libisfreetype-5.2-java, libisnativec-java-lowlvl
> libisfreetype-5.2-java Depends: libisnativec-java-lowlvl
I am still on my self-prescribed mental break from all this. My answer would be
that whoever addresses this issue should work closely with upstream on this.
And if they do not care, neither should Debian. Well, they may be happy about it
to be done for them.
> By the way, the description says
> This package always installs the latest version of the isCWT library.
> It only offers a symbolic link to the respective jar file.
> But I have no idea what isCWT is,
libiscwt-java - abstractions and Java implementations for rendering PDF
> and what that actually means.
Well, this is some disagreement of mine with the rest of pkg-java. It
once implemented ldconfig for java through the Debian packaging mechanism.
That is not appreciated, though.
More information about the pkg-java-maintainers