> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Bob Blick > Sent: Friday, July 25, 2008 12:45 AM > To: avr-chat > Subject: Re: [avr-chat] µC/avr crypto lib > > Hi Eric, > > Ahh, back to reasonable discourse. Good. > > So how can we license code and insure that improvements to it > go back to > the community, while still allowing it to be used in a proprietary > system?
Note that in my original post I also mentioned GPL+exception, which is the license of libgcc (that comes with the compiler). Others (in the past) have pointed out to me that this is different from LGPL. As, I guess, the LGPL has some other issues with it as well that make it non-ideal. Having a library licensed as GPL+exception ensures that any changes to the library remain open and free, but that it can be linked with proprietary applications and those applications can remain proprietary. I'm certainly fine with that choice, and it provides a win-win situation (IMO). The crypto library would see a lot more traffic in that case, and, assuming that the validation is complete, I would then be interested in perhaps including it in WinAVR. _______________________________________________ AVR-chat mailing list AVR-chat@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-chat
