AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2008.11.01 07:10 "[Tiff] example of (standalone) TIFFRegisterCODEC", by Brad Hards
2008.11.14 08:14 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Brad Hards
2008.11.14 16:18 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Frank Warmerdam
2008.11.14 23:32 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Brad Hards
2008.11.16 00:39 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Frank Warmerdam
2008.12.13 10:30 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Brad Hards
2008.12.13 15:18 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Frank Warmerdam
2008.12.13 16:35 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Bob Friesenhahn
2008.12.13 19:12 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Gene Amtower
2008.12.13 21:52 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Bob Friesenhahn
2008.12.14 00:07 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Brad Hards
2008.12.14 05:47 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Bob Friesenhahn
2008.11.14 16:53 "RE: [Tiff] example of (standalone) TIFFRegisterCODEC", by ComSquare Martin Osieka

2008.12.14 05:47 "Re: [Tiff] example of (standalone) TIFFRegisterCODEC", by Bob Friesenhahn

The reason why I included that statement is that a non-trivial amount of the header file is actually from tiffio.h. The copyright on tiffio.h is as shown.

Then it is reasonable.

The other way to deal with this (actually, just avoid the issue) is to include all the new code in existing files. Would that be preferable for licensing or technical reasons?

It does not really avoid the issue but I think that new interfaces are best put in new files.

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/