Re: Help us with GPL / LGPL

[Christopher Roy Bratusek <zanghar freenet de>]

Am Sat, 6 Jun 2009 11:58:33 +0200
schrieb Christopher Roy Bratusek <zanghar freenet de>:

> Am Sat, 06 Jun 2009 15:33:28 +0900 (JST)
> schrieb Teika Kazura <teika lavabit com>:
> 
> > Hi. If someone understands GPL / LGPL, please help us.
> > 
> > Recently Wang Diancheng has sent us a nice code for librep (See May
> > 31 mail, or
> > http://mail.gnome.org/archives/sawfish-list/2009-May/msg00140.html)
> > 
> > The problem is the copyright. Wang Diancheng borrowed code from
> > glib, or more precisely, glib-2.x.y/glib/gutf8.c, which is licensed
> > with LGPL. On the other hand, librep is GPL. Should it be GPL, or
> > LGPL? 
> > 
> > I'd like to know what will be the proper copyright notice, too.
> > 
> > gutf8.c starts as:
> > ------------------------------------------------------------------------
> > /* gutf8.c - Operations on UTF-8 strings.
> >  *
> >  * Copyright (C) 1999 Tom Tromey
> >  * Copyright (C) 2000 Red Hat, Inc.
> >  *
> >  * This library is free software; you can redistribute it and/or
> >   [LGPL preamble follows]
> > ------------------------------------------------------------------------
> > The file by Wang Diancheng, named utf8.c, starts:
> > ------------------------------------------------------------------------
> > /* This file some code come from glib:
> >  * utf8.c - Operations on UTF-8 strings
> >  *
> >  * Copyright (C) 2009 Wang Diancheng.
> >  *
> >  * This library is free software; you can redistribute it and/or
> >   [LGPL preamble follows]
> > ------------------------------------------------------------------------
> > 
> > Is it enough?
> > 
> > # I have never understood GPL. Why not bsd license?
> > 
> > Thanks beforehand,
> > Teika (Teika kazura)
> > 
> 
> aditionally an entry in CREDITS to the glib-devs and that should be
> enough to my knowledge. (That's how I did it all other the time and
> never ran into problems)
> 
> But of course I can't say that I'm 100% sure.
> 
> Chris
> 

ah yes and a COPYING.UTF8 should be added.
I'll do that now.

Chris