tag:blogger.com,1999:blog-5246987755651065286.post6494047103308912915..comments2024-02-22T16:15:42.388-08:00Comments on cbloom rants: 08-05-09 - Relacy License Notescbloomhttp://www.blogger.com/profile/10714564834899413045noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5246987755651065286.post-8635166540568511822009-08-05T13:50:11.586-07:002009-08-05T13:50:11.586-07:00Yeah it's not gonna be exactly LGPL. Stupid l...Yeah it's not gonna be exactly LGPL. Stupid licenses. It's so hard<br />to just put a reasonable simple license on things.cbloomhttps://www.blogger.com/profile/10714564834899413045noreply@blogger.comtag:blogger.com,1999:blog-5246987755651065286.post-86930863884631863582009-08-05T12:26:59.590-07:002009-08-05T12:26:59.590-07:00Relacy itself is under LGPL. Any code that you wri...<i>Relacy itself is under LGPL. Any code that you write which directly uses Relacy must be open sourced. This means your threading test harness and the actual lock free algorithms.</i><br /><br />The LGPL means any code you write which directly uses the code covered by the LGPL (by directly I mean <i>not</i> through a DLL) <i>and which you release as a binary</i> must be made available under the LGPL to whomever you gave the binary. If you never publish a binary of the code that uses the LGPL code, you're under no obligation to release the source to it.Anonymousnoreply@blogger.com