Re: Failure to detect pswrite and epswrite Ghostscript devices

Test User <[email protected]> Mon, 2 Nov 2015 00:11:36 -0500
Newsgroups gmane.comp.video.graphicsmagick.bugs
Message-ID <CAH7jLru5W32_oTW9OtHpyHKO8VcKvQNOWcBPoiWc5OcyrdZY-g@mail.gmail.com>
--===============1171112006485799654==
Content-Type: multipart/alternative; boundary=089e01160712be5623052387cf62

--089e01160712be5623052387cf62
Content-Type: text/plain; charset=UTF-8

On Sun, Nov 1, 2015 at 11:25 PM, Bob Friesenhahn <
[email protected]> 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.

--089e01160712be5623052387cf62
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Nov 1, 2015 at 11:25 PM, Bob Friesenhahn <span dir=3D"ltr">&lt;=
<a href=3D"mailto:[email protected]" target=3D"_blank">bfriesen@=
simple.dallas.tx.us</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><span class=3D"">On Sun, 1 Nov 2015, Test User wrote:<b=
r>
&gt;<br>
</span><span class=3D"">&gt; Are you saying that if I *did* build an applic=
ation that depended on,<br>
&gt; for example, libGraphicsMagick-3.dll (with the Ghostscript library opt=
ion<br>
&gt; enabled, whichit isnot in my case), I would have to distribute the sou=
rce of<br>
&gt; my application because Ghostscript infected GraphicsMagick which in tu=
rn<br>
&gt; infected my application, and the way to avoid this would be to use GNU=
<br>
&gt; Ghostscript (downloaded from a GNU mirror site)?<br>
<br>
</span>Looking at older Artifex license statements (retrievable via the<br>
Wikipedia page on Ghostscript), it seems that even the GPL version<br>
(starting with some version) has a similar problem.<br></blockquote><div><b=
r></div><div>Yes, that makes sense. The LGPL is the one that stops the &quo=
t;infection&quot;,<br></div><div>but GNU Ghostscript is GPL.<br><br>&lt;sni=
p /&gt;<br><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
In my opinion (I am not a lawyer) there should not be an &quot;infection&qu=
ot;<br>
from GPL or AGPL if Ghostscript is run as a separate program rather<br>
than a library.</blockquote><div><br></div><div>That has always been my und=
erstanding. <br><br></div><br></div>By the way, I noticed the following in =
the configure script:<br># It would be nice to use reg.exe to obtain Ghosts=
cript information<br># but unfortunately MSYS seems to transform registry k=
ey paths into<br># filesystem paths so it does not work.=C2=A0 Maybe there =
is a way to<br># prevent that translation?<br><br></div><div class=3D"gmail=
_extra">Does the following solve that problem?<br>$ cmd /c &quot;reg query =
\&quot;HKLM\Software\GPL Ghostscript\&quot; /s&quot;<br><br>HKEY_LOCAL_MACH=
INE\Software\GPL Ghostscript\9.18<br>=C2=A0=C2=A0=C2=A0 GS_DLL=C2=A0=C2=A0=
=C2=A0 REG_SZ=C2=A0=C2=A0=C2=A0 C:\Program Files (x86)\gs\gs9.18\bin\gsdll3=
2.dll<br>=C2=A0=C2=A0=C2=A0 GS_LIB=C2=A0=C2=A0=C2=A0 REG_SZ=C2=A0=C2=A0=C2=
=A0 C:\Program Files (x86)\gs\gs9.18\bin;C:\Program Files (x<br>86)\gs\gs9.=
18\lib;C:\Program Files (x86)\gs\gs9.18\fonts<br><br></div><div class=3D"gm=
ail_extra">Regards,<br></div><div class=3D"gmail_extra">Test User.<br></div=
><div class=3D"gmail_extra"><br></div></div>

--089e01160712be5623052387cf62--


--===============1171112006485799654==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1171112006485799654==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Graphicsmagick-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/graphicsmagick-bugs

--===============1171112006485799654==--