Hi, Quoting Paul Wise (2014-08-29 17:02:35) > On Fri, Aug 29, 2014 at 6:52 AM, Johannes Schauer wrote: > > the upstream of fuzzylite relicensed from apache 2.0 to LGPL 3.0 with the > > release of fuzzylite 5.0 (but not the versions prior to that). So if > > upstream should upgrade their copy of the embedded fuzzylite, then the > > license problem should go away. > > Please ask vmci upstream to remove the embedded copy of fuzzylite and > depend on the system version. > > https://wiki.debian.org/EmbeddedCodeCopies
Would this solve the license incompatibility between fuzzylite (apache 2.0) and vcmi (gpl2+)? I asked upstream whether they can remove the embedded copy and depend on the system version instead: http://bugs.vcmi.eu/view.php?id=1886 Currently, fuzzylite is not in Debian nor does any other software in Debian carry an embedded copy of it (at least according to codesearch.d.n). This is why I did not consider packaging fuzzylite separately yet. But if it would solve the licensing problem, then I will certainly see if I can get fuzzylite packaged. A problem might be that vcmi as the only user of that library uses the old 4.0 version while upstream just released 5.0. Vcmi upstream expressed that migration to fuzzylite 5.0 would be very troublesome here: http://bugs.vcmi.eu/view.php?id=1884#c4932 Would it be okay to package fuzzylite 4.0 even though upstream is at 5.0? cheers, josch -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140829151623.3685.12351@hoothoot
