On Jan 17, 2009, at 5:03 PM, Stuart Sierra wrote:
>
> On Dec 31 2008, 5:16 am, lpetit wrote:
>> I re-read my original post, and it seems clear to me : I stated I
>> wish
>> to embed swank-clojure files into clojure-dev plugin.
>
> I do not see a conflict here, provided you do not modify swank
On Dec 31 2008, 5:16 am, lpetit wrote:
> I re-read my original post, and it seems clear to me : I stated I wish
> to embed swank-clojure files into clojure-dev plugin.
I do not see a conflict here, provided you do not modify swank-clojure
and clearly indicate that it is under a separate license.
On Dec 31 2008, 6:48 am, lpetit wrote:
> OOps, I'm losing memory, I answered twice to the e-mail ;-)
>
> On 31 déc, 11:16, lpetit wrote:
>
> > Yes, this is what I remember from LGPL. But anyway, swank-clojure is
> > not LGPL, it's GPL.
I suspect you can't distribute the swank-clojure files w
OOps, I'm losing memory, I answered twice to the e-mail ;-)
On 31 déc, 11:16, lpetit wrote:
> Yes, this is what I remember from LGPL. But anyway, swank-clojure is
> not LGPL, it's GPL.
>
> I re-read my original post, and it seems clear to me : I stated I wish
> to embed swank-clojure files into
Yes, this is what I remember from LGPL. But anyway, swank-clojure is
not LGPL, it's GPL.
I re-read my original post, and it seems clear to me : I stated I wish
to embed swank-clojure files into clojure-dev plugin.
Anyway, I'll rephrase my question differently :
Given that :
- Clojure-dev's (an
lpetit writes:
> So swank-clojure will not be hard-linked (at compilation time) to any
> of clojure-dev code. Nor will it be dynamically linked to any clojure-
> dev code at runtime : it will be dynamically linked to the clojure
> environment launched by clojure-dev on behalf of the user.
>
> Bu
On 30 déc, 23:55, "Mark H." wrote:
> On Dec 30, 10:26 am, Phil Hagelberg wrote:
> Actually the LGPL allows linking to the library (somewhat different
> than "using the code") from any program, even one which is not under
> an open-source license. "L" used to stand for "library" and the
> canoni
On Dec 30, 10:26 am, Phil Hagelberg wrote:
> lpetit writes:
> > I'm not sure. From what I remember, what you describe is more related
> > to LGPL ?
>
> No, the LGPL allows using the code in another program that is Free but
> not GPL-licensed.
Actually the LGPL allows linking to the library (som
lpetit writes:
> I'm not sure. From what I remember, what you describe is more related
> to LGPL ?
No, the LGPL allows using the code in another program that is Free but
not GPL-licensed. If you're just distributing some code from
swank-clojure, licensing conflicts will never come into play. It
I'm not sure. From what I remember, what you describe is more related
to LGPL ?
On 30 déc, 18:19, Phil Hagelberg wrote:
> lpetit writes:
> > So I guess that if for clojure-dev (eclipse plugin for clojure) we
> > want to use it for interactivity with an external clojure environment,
> > and we
lpetit writes:
> So I guess that if for clojure-dev (eclipse plugin for clojure) we
> want to use it for interactivity with an external clojure environment,
> and we want to start the environment from the plugin, we have a
> problem : stop me if I'm wrong, but if any file of swank-clojure is
> e
Sorry for this e-mail that could be more targeted to Jeffrey Chu, but
I was unable to find its direct e-mail address, and I know he is a
clojure ml member, so ...
It seems that swank-clojure license is a flavor of GPL ("License as
distributed with Emacs").
So I guess that if for c
12 matches
Mail list logo
