* Richard Braakman <[EMAIL PROTECTED]> [2001/07/22 17:42]:
> On Sun, Jul 22, 2001 at 03:03:50PM +0200, Rafael Laboissiere wrote:
> > My problem here is the following: let us say that L1 is released under the
> > LGPL. Now, imagine that some non-free software links against L1. "No
> > problem, L1
On Sun, Jul 22, 2001 at 03:03:50PM +0200, Rafael Laboissiere wrote:
> My problem here is the following: let us say that L1 is released under the
> LGPL. Now, imagine that some non-free software links against L1. "No
> problem, L1 is LGPL'd", you would say. But, hey!, L1 links against L2,
> which
* Raul Miller <[EMAIL PROTECTED]> [2001-07-22 08:46]:
> On Sun, Jul 22, 2001 at 12:39:03PM +0200, Rafael Laboissiere wrote:
> > I need an advice about library license.
> >
> > If I develop a library L1 that links to another library L2 which is
> > GPL'd, could I release L1 under the LGPL, or am I
On Sun, Jul 22, 2001 at 12:39:03PM +0200, Rafael Laboissiere wrote:
> I need an advice about library license.
>
> If I develop a library L1 that links to another library L2 which is
> GPL'd, could I release L1 under the LGPL, or am I forced to release L1
> under the GPL?
You're not forced to rele
I need an advice about library license.
If I develop a library L1 that links to another library L2 which is GPL'd,
could I release L1 under the LGPL, or am I forced to release L1 under the
GPL?
Plese, Cc: replies to me. Thanks.
--
Rafael Laboissiere, Debian developer
5 matches
Mail list logo