Spotting GPL violations
Jeroen Dekkers
jeroen at vrijschrift.org
Sun Dec 12 15:13:22 UTC 2004
At Sun, 12 Dec 2004 14:45:03 +0000,
Philip Webster wrote:
> I've contacted the author, and raised the points we have both covered on
> this list. I can report that this is in fact NOT a GPL violation, or at
> least so far as I can see. Here's how the RISC OS interface works:
>
> GemPrint (the proprietary interface) links !Printers (the RISC OS
> printing system) to GIMP-Print (a Free printing system which supports
> many more models of printer than !Printers ever could.) !Printers is
> proprietary, and GemPrint links to it using what are essentially RISC OS
> libraries.
>
> The link between GemPrint and GIMP-Print is done via a temp file. A RISC
> OS application invokes !Printers by requesting that something is
> printed, and !Printers calls GemPrint. GemPrint saves GIMP-Print
> compatible data to a file, and GIMP-Print comes along later, sees the
> file, and prints it.
>
> GemPrint is careful never to directly invoke the GPL-licensed library at
> any time.
>
> As far as I'm concerned, this means there is no GPL violation. Unless
> you can see anything wrong with the system as described above.
No, I don't see any problem either. I was actually suspecting that it
worked like this, but I couldn't judge from the homepage only.
Jeroen Dekkers
More information about the Discussion
mailing list