|
Re: Writing an exception to LGPL for a C++ template library: msg#00049org.fsf.europe.discussion
Hi Federico, Thanks for your answers. The reasons why we were considering using the LGPL, not the GPL, are that: - we need to make sure LGPL-licensed software (apps,libs,everything) can use our library without any worry. - we don't care too much if proprietary software uses our lib (though we wouldn't rejoice about that either). The exception in the GCC C++ std. library is: I am glad you mention it because this is something we have looked at, but we were left with a big question open: what would we have to change in the formulation of this exception in order to make it applicable to the LGPL instead of GPL ? Is such a transposition possible at all? We would also have to modify it to apply to all software, not only libraries. Benoit |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: article on GPLv3, Linux kernel, and Devices Rigged to Malfunction: 00049, Rui Miguel Silva Seabra |
|---|---|
| Next by Date: | Re: article on GPLv3, Linux kernel, and Devices Rigged to Malfunction: 00049, Rui Miguel Silva Seabra |
| Previous by Thread: | Re: Writing an exception to LGPL for a C++ template libraryi: 00049, Federico Montesino Pouzols |
| Next by Thread: | Re: Writing an exception to LGPL for a C++ template library: 00049, Federico Montesino Pouzols |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |