On Wed, 2011-01-12 at 23:19 +1100, Scott Penrose wrote: > It is grey, because technically GPL is supposed to only link in GPL. > I think LGPL should be OK too. It better had be, since there's a shed-load of GPLed code out there that relies on LGPL libraries.
> Sorry, but they are not open source. Like many other DLL that you link > to. You can download the DLL though. You should be able to link in and > use the DLL. The DLL is still distributed, but I don't believe the > code can be, without loosing its purpose (ie. to upload approved IGC > files to OLC). > Would it be sensible to release its API documentation under LGPL or some equivalent license or would that break IGC rules by enabling J. Random Programmer to use the DLL? > How this is going to apply in the future, and new platforms ? Not > sure. > Agreed. I'm somewhat mystified by this. There would seem to be some conflict between the IGC intention of having the validation code hidden in the logger firmware where it can only be used by the logger and distributing a binary module that any program can use to sign a log file. So, presumably there has to be some restrictions on who can use the DLL, what program it can be used it and what it can be used for, e.g. signing a log file vs. checking that a signature is valid. Martin ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Xcsoar-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcsoar-user
