-
2007.07.14 23:29 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Jay Berkenbilt
-
2007.07.15 00:27 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Bob Friesenhahn
- 2007.07.15 04:37 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Ron
- 2007.07.15 11:17 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev
-
2007.07.16 09:04 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andy Cave
- 2007.07.16 11:39 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev
- 2007.07.16 11:51 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Graeme Gill
- 2007.07.16 12:01 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Ron
- 2007.07.16 15:23 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Bob Friesenhahn
- 2007.07.15 11:23 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev
-
2007.07.15 00:27 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Bob Friesenhahn
2007.07.16 11:39 "Re: [Tiff] [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev
On 7/16/07, Andy Cave <andy.cave@hamillroad.com> wrote:
So what happens if someone builds a standalone piece of s/w (tiffjbigdecomp) that reads (compressed) data from stdin and writes (uncompressed) data to stdout. They can then write s/w that execs a sub-process, redirecting stdin/stdout to be a file on disk and a pipe, and then just read the decompressed data from the pipe. Does that infringe GPL? I think not (as otherwise no commercial s/w could run on Linux), in which case I think the claim that dynamic loading / linking does (infringe GPL) is not necessarily solid, as the difference between that and dynamic linking to a library is pretty thin.
Andy,
I am pretty sure that this question can be answered in court only. But GPL FAQ discuss this case a bit:
http://www.gnu.org/licenses/gpl-faq.html#MereAggregation
http://www.gnu.org/licenses/gpl-faq.html#NFUseGPLPlugins
Best regards,
Andrey
--
Andrey V. Kiselev
ICQ# 26871517