Re: The "regex" module brings in GPLv3 code even with --lgpl

2017-05-09 Thread Ævar Arnfjörð Bjarmason
On Mon, May 8, 2017 at 9:43 PM, Bruno Haible wrote: > Ævar Arnfjörð Bjarmason wrote: >> > When you use the --lgpl option to gnulib-tool, it should replace the >> > copyright headers of the files accordingly. If not, that's a bug in >> > gnulib-tool. >>

Re: The "regex" module brings in GPLv3 code even with --lgpl

2017-05-08 Thread Ævar Arnfjörð Bjarmason
On Mon, May 8, 2017 at 8:22 PM, Bruno Haible wrote: > Hi Ævar, > >> The regex.c module depends on regex_internal.h, which depends on >> intprops.h, which depends on verify.h, which is GPLv3, not LGPL like >> the rest of the regex module. > > verify.h is under LGPLv2+. As described in >

Re: The "regex" module brings in GPLv3 code even with --lgpl

2017-05-08 Thread Ævar Arnfjörð Bjarmason
On Mon, May 8, 2017 at 7:39 PM, Paul Eggert wrote: > Thanks for reporting that. I installed the attached, which I hope fixes the > problem. Great, that looks much better than my monkeypatch & solves the problem. I.e. no GPLv3 header dependency anymore.

The "regex" module brings in GPLv3 code even with --lgpl

2017-05-08 Thread Ævar Arnfjörð Bjarmason
The regex.c module depends on regex_internal.h, which depends on intprops.h, which depends on verify.h, which is GPLv3, not LGPL like the rest of the regex module. I'm using the equivalent of the patch at the end of this E-Mail to import the engine into a GPLv2 only project, but this seems like a