On Tue, 2006-06-20 at 23:09 +1100, Martin Desruisseaux wrote: > Jody Garnett a écrit : > >> [...snip...] The Proj4 copyright header is already copied below the > >> Geotools copyright header in the source files. We need (maybe by a > >> layer) to verify if the Proj4 license conflict with the LGPL license > >> (Proj4 license is opensource, but do we need to distribute the projection > >> files under an other license than LGPL?). Frank Warmerdam could > >> probably answer since he is the Proj4 maintainer :). > > > Ug, I would prefer not to mix licenses if we can avoid it. > > I'm fine with that, but how to process? Do we abandon the LGPL license for > the files derived from > Proj4 code? Keeping in mind that the same files contains also a lot of > Geotools-specific code. I'm > fine with either solution - would just like to know what is the appropriate > action. >
You can't license anything under more than one license; such an idea makes no sense. (Dual licensing means that an entity can choose one of several licenses to use in any particular case, but in each case the code is always released under a single license.) Generally, the more restrictive license wins. You need to figure out, from the language, if the Proj4 code can be re-licensed LGPL without violating the terms of the Proj4 license. If not, then GeoTools has a real copyright problem; GeoTools can't call itself LGPL if one or more files have a conflicting license. So either you need to ask Frank W. to relicense the Proj4 code we need or we have to replace the code. --adrian _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
