AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
July 2007

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2007.07.14 08:15 "[ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev
2007.07.14 23:29 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Jay Berkenbilt
2007.07.15 00:27 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Bob Friesenhahn
2007.07.15 04:37 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by <ron@debian.org>
2007.07.15 04:41 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Graeme Gill
2007.07.15 11:17 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev
2007.07.16 09:04 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andy Cave
2007.07.16 11:39 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev
2007.07.16 11:51 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Graeme Gill
2007.07.16 12:01 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by <ron@debian.org>
2007.07.16 12:19 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andy Cave
2007.07.16 12:33 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev
2007.07.16 13:22 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andy Cave
2007.07.16 15:23 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Bob Friesenhahn
2007.07.15 11:23 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Andrey Kiselev

2007.07.15 04:41 "Re: [ANNOUNCE]: Libtiff 4.0.0alpha released", by Graeme Gill

Ron wrote:
> Yes, I've had similar (though less authoritative) advice regarding
> mixing GPL software with openssl, which otherwise needs an explicit
> exception to the GPL for individual works which intend to permit that.

> This does seem logical, since if you are using symbols from the library
> then you are linking to it.  That they may be provided statically, or
> through the ELF dynamic linker, or by explicit dynamic loading from the
> application (etc.) doesn't really change that much.

I don't believe that the nature of the link between the GPL
code and other code that goes to make up a package of
functionality has anything directly to do with it. It's
the fact that a distributed package ("work") depends on
GPL code for some of its functionality that makes the
distributed package a derived work. If the different pieces
do directly link then this is more obviously established,
but the GPL code could be in a separate executable and
still the package may be a derived work.

Graeme Gill.