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

Re: License change for ghostscript



On 07/31/2009 04:19 PM, Tim Waugh wrote:
On Fri, 2009-07-31 at 22:47 +0300, Ville Skyttä wrote:
This might cause problems for a bunch of packages.

$ repoquery --repoid=rawhide --whatrequires --alldeps ghostscript ghostscript-
gtk --qf="%{NAME}: %{LICENSE}" | grep -vP '\bGPL(v3|\S*\+)' | sort

Wouldn't it be packages using the libraries that might pose problems?

$ repoquery --repoid=rawhide --whatrequires --alldeps
'libgs.so.8()(64bit)' 'libijs-0.35.so()(64bit)' --qf="%{NAME}:
%{LICENSE}"
foomatic: GPLv2+
ghostscript-devel: GPLv2 and Redistributable, no modification permitted
libspectre: GPLv2+
ImageMagick: ImageMagick
ghostscript: GPLv2 and Redistributable, no modification permitted
ghostscript-gtk: GPLv2 and Redistributable, no modification permitted
ghostscript-devel: GPLv2 and Redistributable, no modification permitted
gutenprint: GPLv2+

Other packages would be invoking the executable, which (AIUI) is not
considered "based on" ghostscript.

The ImageMagick license seems to be compatible with GPLv3.

I'm really only concerned about these library linking cases, which all seem to be GPLv3 compatible.

I think it is a reasonable argument that applications which call out to ghostscript are well separated, thus, can be sanely treated as two separate programs.

~spot


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