Thanks Elliot!  I missed that.

Cheers,
   Kevin


On Sat, Aug 30, 2014 at 12:00 PM, Elliot Saba <[email protected]> wrote:

> In the tarball, there is a file called FOSSEXCEPTION, here's a mirror on
> github
> <https://github.com/UCSCReconGroup/kyotocabinet/blob/master/FOSSEXCEPTION>.
>  I don't pretend to understand all the linking subtleties going on here,
> but from this thread <https://github.com/JuliaLang/julia/issues/1598>,
> since kytotocabinet is GPL, and this piece of software cannot really be
> used without kyotocabinet, it will be "infected" by GPL as soon as the user
> tries to actually use it in conjunction with the GPL.  Since Dmitry has
> released it as MIT, if someone were to make a derivative work of only his
> package and remove kyotocabinet completely, it would then be able to be
> completely MIT.
>
> This might be the exact same thing as what Kevin just said, but oh well.
> ;)  I think the best thing to do here is just to notify users that using
> this package means you're using a GPL3 library.
>  -E
>
>
> On Sat, Aug 30, 2014 at 2:19 PM, Kevin Squire <[email protected]>
> wrote:
>
>> Just curious where you saw BSD listed--I couldn't find it anywhere.
>>
>> If you download the tar ball (
>> http://fallabs.com/kyotocabinet/pkg/kyotocabinet-1.2.76.tar.gz), COPYING
>> shows the license as GPL3.  My understanding is that if you link to that
>> library (which likely includes using it from Julia)*, your application
>> becomes GPL3.  However, Dmitry can license his code under whatever he
>> wants, and if someone wanted to, they could use it as the basis for, say
>> Redis, or berkeleyDB.  (I have no idea if that would actually be a good
>> idea.)
>>
>> Cheers,
>>    Kevin
>>
>> * There are some subtlties which I used to understand better, but don't
>> really anymore.
>>
>>
>> On Sat, Aug 30, 2014 at 10:19 AM, Elliot Saba <[email protected]>
>> wrote:
>>
>>> Ah, I see, as long as your application is opensource and is licensed
>>> under one of the licenses they list, (BSD is listed there, so I imagine MIT
>>> is acceptable to them) you don't have to buy a commercial license.  Good to
>>> know.
>>> -E
>>>
>>>
>>> On Sat, Aug 30, 2014 at 12:41 PM, Kevin Squire <[email protected]>
>>> wrote:
>>>
>>>> Hi Elliot,
>>>>
>>>> Just to clarify, the KyotoCabinet license is actually GPLv3, with the
>>>> option to purchase a separate commercial license.  (One has to download the
>>>> source to actually see the license.)  But I agree that it's a good idea to
>>>> clarify the license situation.
>>>>
>>>> Cheers,
>>>>    Kevin
>>>>
>>>>
>>>> On Sat, Aug 30, 2014 at 8:28 AM, Elliot Saba <[email protected]>
>>>> wrote:
>>>>
>>>>> Cool!  I've used KyotoCabinet before, so it's nice to see this coming
>>>>> in to Julia!  Your code looks really nice, the only thing I can think of 
>>>>> to
>>>>> add is perhaps a notice to LICENSE.md that while your code is 
>>>>> MIT-licensed,
>>>>> KyotoCabinet is not.  It's free for personal use, but commercial use
>>>>> requires a commercial license <http://fallabs.com/license/>.
>>>>>
>>>>> One other thing worth mentioning is that because you have *@osx
>>>>> Homebrew* in your REQUIRES file, you don't need to check for *if
>>>>> Pkg.installed("Homebrew") *in your deps/build.jl file.  You can just
>>>>> delete that if statement, we never need to have those ever again, now that
>>>>> we have conditional requirements in Pkg.
>>>>>  -E
>>>>>
>>>>>
>>>>> On Sat, Aug 30, 2014 at 1:00 AM, Dmitry Semyonov <[email protected]
>>>>> > wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I used KyotoCabinet <http://fallabs.com/kyotocabinet/> key-value
>>>>>> storage in some of my Python projects, but couldn't find bindings for
>>>>>> Julia. So I wrote something by myself. Hope it might be useful for 
>>>>>> someone
>>>>>> else.
>>>>>>
>>>>>> Here is the source: https://github.com/tuzzeg/kyotocabinet.jl
>>>>>>
>>>>>> I am pretty new in Julia world, so if you have comments, code
>>>>>> style/performance/design suggestions - I'd love to hear them.
>>>>>>
>>>>>> Cheers,
>>>>>> Dmitry
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to