On 08/25/2010 01:29 AM, Onkar Shinde wrote:
> On Wed, Aug 25, 2010 at 10:41 AM, tony mancill <tmanc...@debian.org> wrote:
>> On 08/24/2010 08:01 PM, Thadeu Lima de Souza Cascardo wrote:
>>> Package: libjcharts-java
>>> Version: 0.7.5-1
>>> Severity: normal
>>>
>>> libjcharts-java depends on openjdk or sun jre explictly. It does not
>>> allow the use of other java runtime (like gcj), which would be possible
>>> if it depended on java5-runtime, for example. I don't know what version
>>> is needed for libjcharts-java, so I am not providing a patch.
>>>
>>> It already depends on another java library (libbatik-java), which
>>> depends on java2-runtime-headless. I am not sure libjcharts-java is
>>> headless, but this should also be considered.
>>
>> Given that this source package only generates a single library package
>> which doesn't appear that it's used as a stand-alone app (I may be
>> incorrect on that, but I didn't see anything about it on the jCharts
>> site), there needn't be a runtime JRE dependency at all.
>>
>> Any objections to removing the JRE from Depends completely?
> 
> IIRC, jcharts uses some Sun specific APIs which are only available in
> Sun JRE and OpenJDK JRE.
> If this isn't the case then the restricted dependencies is a packaging
> mistake on my part. Please feel free to remove JRE dependency after
> verification.
> 
> 
> Onkar

Hi Onkar,

That would be a good reason for the runtime dependency.  :)  Since I
don't have any sort of a comprehensive test suite for jcharts and you
have already looked at the issue at least once when packaging it
initially, I think it's best to leave the package as is for the short term.

Thadeu, have you tested jcharts with gcj?  If so, do you have an idea of
how much coverage that testing provides?

Thank you,
tony

Attachment: signature.asc
Description: OpenPGP digital signature

__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers>. Please 
use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to