Hi,
nice,
I will try today how it would be possible to replace and validate when
someone change parts of say the core, not the whole core though.
Best regards,
Martin
On 01/26/2015 10:46 PM, Hauke Petersen wrote:
Nice!
I'm too tired to really think through it, but how does this fit in
when keeping parts more close to the hardware proprietary? Say I don't
want to publish my device driver, and maybe I don't want to share my
pin-mapping?
Cheers,
Hauke
On 26.01.2015 16:43, Kaspar Schleiser wrote:
Hey guys,
here's an initial draft on how to check for LGPL compliance:
https://github.com/RIOT-OS/RIOT/wiki/LGPL-compliancy-guide
This is for showing that some proprietary code has been compiled and
linked with a specific version of RIOT.
I wrote the wiki entry out of my head, so maybe I missed something,
but the general method worked in prior testing. ;)
Should we go and automate this, or am I missing something?
Kaspar
p.s.: This is in no way any conclusion to the license discussion, see
it as purely technical please.
_______________________________________________
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
