|
From: Michael B. <mb...@de...> - 2021-10-13 14:06:40
|
Hi, On Wed, Oct 13, 2021 at 03:30:23PM +0200, Andrew Dalke wrote: > > On Oct 13, 2021, at 14:46, Norwid Behrnd via InChI-discuss > > <inc...@li...> wrote: > > > > the assigned license is not compatible with one of those Debian > > requests. > > Could you elaborate? It's section 15: |15. If you modify the Library in any way whatsoever, the output from any |such modified Library may not be referred to as ‘InChI’ or any similar |name. Any attempt to refer to such output as ‘InChI’ will automatically |terminate your rights under this Licence. See also the discussion on this list from February. > The InChI license for version 1.06 says: > > 3. You may opt to apply the terms of the ordinary GNU General > Public Licence instead of this Licence to a given copy of the > Library. To do this, you must alter all the notices that refer > to this Licence, so that they refer to the ordinary GNU General > Public Licence, version 2, instead of to this Licence. (If a > newer version than version 2 of the ordinary GNU General Public > Licence has appeared, then you can specify that version instead > if you wish.) Do not make any other change in these notices. > > Once this change is made in a given copy, it is irreversible for > that copy, so the ordinary GNU General Public Licence applies to > all subsequent copies and derivative works made from that copy. > > GPLv2 and GPLv3 are both compatible with Debian. > > Is there a reason DebiChem cannot exercise this clause? Debian could ship inchi under the GPL, but which program (other than OpenBabel, which is GPLv2 due to historical reasons) would use that? Certainly not RDKit or other non-GPL ones. Michael |