Re: Failure to detect pswrite and epswrite Ghostscript devices

On Sun, 1 Nov 2015, Test User wrote:

> ./configure fails to detect the pswrite and epswrite Ghostscript devices
> because the names are now ps2write and eps2write. For example:

Thanks for the heads-up on this.  Ghostscript (and MinGW) are always a 
moving target, and many versions are in use.

What version of Ghostscript are you using?  Is it a commercial, 
Artifex AFPL, AGPL, or a GNU (GPL) version?

The licensing terms for AGPL Ghostscript seem to be rather draconian:
"http://www.artifex.com/page/licensing-information.html".

The Artifex GPL and AGPL license (as stated) is not strictly the GPL 
or AGPL license since those licenses do not require that all of the 
rest of the source code of the whole program (including the program 
which ran it) be GPL (and then AGPL) licensed.  GPL and AGPL only 
requires that the source be distributed and that its license be 
compatible with the GPL or AGPL license.

There is no Ghostscript code in GraphicsMagick and only external 
execution (fork/exec) or dynamic loading using a well-defined 
interface are used.  The GraphicsMagick project is MIT/X11 licensed 
(compatible with AGPL and GPL) and we do not distribute Ghostscript 
binaries.

Users are on their own to comply with Artifex license terms for the 
version they chose to use and their own unique situation.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------