Hello,

I am trying to package bluej [1], a Java program, but I think there is a 
license problem. 
This program uses a library that is not free (AppleJavaExtensions.jar). 
Apparently, the use of this library is only to build the MacOS version of the 
program. I think I could change the upstream source and achieve that the 
software won't be dependent on this library (now it is). But I don't know if 
it's worth to do it...

Otherwise, the upstream source (orig.tar.gz) would include all this non-free 
software.

Could this package be in main archive area or will it be considered as a 
non-free software, although I make this changes? If it is considered as 
non-free software, I'm not interested in packaging it...

What do you do in this cases? What do you recommend?

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585696
-- 
Mònica

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to