Re: [GM-bugs] Failure to detect pswrite and epswrite Ghostscript devices

[Test U. <tes...@gm...>]

On Sun, Nov 1, 2015 at 11:25 PM, Bob Friesenhahn <
bfr...@si...> wrote:

> On Sun, 1 Nov 2015, Test User wrote:
> >
> > Are you saying that if I *did* build an application that depended on,
> > for example, libGraphicsMagick-3.dll (with the Ghostscript library option
> > enabled, whichit isnot in my case), I would have to distribute the
> source of
> > my application because Ghostscript infected GraphicsMagick which in turn
> > infected my application, and the way to avoid this would be to use GNU
> > Ghostscript (downloaded from a GNU mirror site)?
>
> Looking at older Artifex license statements (retrievable via the
> Wikipedia page on Ghostscript), it seems that even the GPL version
> (starting with some version) has a similar problem.
>

Yes, that makes sense. The LGPL is the one that stops the "infection",
but GNU Ghostscript is GPL.

<snip />

In my opinion (I am not a lawyer) there should not be an "infection"
> from GPL or AGPL if Ghostscript is run as a separate program rather
> than a library.


That has always been my understanding.


By the way, I noticed the following in the configure script:
# It would be nice to use reg.exe to obtain Ghostscript information
# but unfortunately MSYS seems to transform registry key paths into
# filesystem paths so it does not work.  Maybe there is a way to
# prevent that translation?

Does the following solve that problem?
$ cmd /c "reg query \"HKLM\Software\GPL Ghostscript\" /s"

HKEY_LOCAL_MACHINE\Software\GPL Ghostscript\9.18
    GS_DLL    REG_SZ    C:\Program Files (x86)\gs\gs9.18\bin\gsdll32.dll
    GS_LIB    REG_SZ    C:\Program Files (x86)\gs\gs9.18\bin;C:\Program
Files (x
86)\gs\gs9.18\lib;C:\Program Files (x86)\gs\gs9.18\fonts

Regards,
Test User.