2016-03-08 3:00 GMT+01:00 Thomas D. <[email protected]>: > Hi, > > Rainer wrote: >> I need to go through it as well. So far, it's a 99.9% fork of json-c, so >> whatever license applies there, applies here as well. But I'll do an audit >> ASAP, which means Feb, 14th at earliest. > > Any updates? Need to know the license for packaging ;-) > > JSON-C uses MIT [1].
If you are fine with JSON-C claiming MIT, than libfastjson does do so also. The GPLv2 parts stem back to json-c, I did not do any changes to the licenses. So I think it is fair to use the same license information. Please let me know if that solves the issue for you. Rainer > > > [1] https://github.com/json-c/json-c/wiki#license > > > -Thomas > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of > sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T > LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
