Hi Pancake, pancake wrote on Thu, Oct 27, 2011 at 06:03:13PM +0200:
> Sorry for the lag and the silence. I've been pretty busy and was > unable to reply in this thread. No problem with the delay, your time is your own to spend. However, i'm not sure this discussion is apropriate on tech@. You are not sending patches. Next time, consider using misc@. > There was a confussion with the bug report that I want to clarify. > > In radare2 I took libc/regex and usr.bin/file from the OpenBSD CVS. > I was looking for some smart implementations of regex and magic to > be used in my project and make it more portable. After a long > evaluation I found that the OpenBSD ones was the shorter and nicer > to maintain. Well, that's a completely different question, not at all related to file(1). > During the merge process I found some C missuses which caused > crashes and problems in file.. I already report them to Edd Barret. > So I think they should be already fixed in mainstream. > > The problem I'm facing now is in libr/util/regex which is the > imported version of OpenBSD's lib/libc/regex. > > The issue was reported by the Debian maintainer of r2 and it's a > license issue. > > http://radare.org/cgi-bin/hg/radare2/file/41de633fa424/libr/util/regex > > If you look at the COPYRIGHT file you'll see that this BSD license > includes the 4th clause which is GPL incompatible and therefore > problematic for Debian to be packaged. I don't see the 4th Berkeley clause in there, but i do see that it was removed 8 years ago: http://www.openbsd.org/cgi-bin/cvsweb/ \ src/lib/libc/regex/COPYRIGHT.diff?r1=1.2;r2=1.3 Once again, it seems unclear what you are talking about. Maybe you are talking about something else, not the 4th Berkeley clause? If so, what exactly? Yours, Ingo > The thing is that there's no .c file in the same directory that > contains such clause, all the code is under 2 or 3 bsd clauses which > are ok for Debian. > > I want to clarify if this 4th clause is inherited to the C code or > it's just a license bug or what. > > r2-0.8.8 release is locked by this issue, so it would be great if we > can fix it asap.
