Re: Combining proprietary code and GPL for in-house use
Henning Makholm <firstname.lastname@example.org> writes:
> LGPL achieves it too. The only extra thing GPL says is that
> "if you reuse my code, I'm not satisfied that you keep MY
> code free. The code YOU write by yourself must also have MY
Well, that depends on the case. I'm generally happy with the LGPL
> Secrecy fulfills no rational purpose at all here. You cannot fix
> your hole without making its existense public, and - contrary
> to software security - there is *no way* to retroactively fix the
> compromised implementations already employed.
Hrm, there is some merit to what you say here.