From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] mxml: add license information
Date: Wed, 01 Aug 2012 22:24:45 +0200 [thread overview]
Message-ID: <5019908D.7080205@lucaceresoli.net> (raw)
In-Reply-To: <20120801201023.05c53086@skate>
Thomas Petazzoni wrote:
> Le Wed, 1 Aug 2012 07:48:58 +0300,
> Baruch Siach <baruch@tkos.co.il> a ?crit :
>
>> +MXML_LICENSE = LGPLv2+
>> +MXML_LICENSE_FILES = COPYING
>
> I haven't applied this one, because the situation is a bit more
> complicated here. mxml is released under LGPLv2+ + some special
> exceptions. See the COPYING file:
>
> Mini-XML License
> September 18, 2010
>
>
> The Mini-XML library and included programs are provided under the
> terms of the GNU Library General Public License version 2 (LGPL2)
> with the following exceptions:
>
> 1. Static linking of applications to the Mini-XML library
> does not constitute a derivative work and does not require
> the author to provide source code for the application, use
> the shared Mini-XML libraries, or link their applications
> against a user-supplied version of Mini-XML.
>
> If you link the application to a modified version of
> Mini-XML, then the changes to Mini-XML must be provided
> under the terms of the LGPL2 in sections 1, 2, and 4.
>
> 2. You do not have to provide a copy of the Mini-XML license
> with programs that are linked to the Mini-XML library, nor
> do you have to identify the Mini-XML license in your
> program or documentation as required by section 6 of the
> LGPL2.
>
>
> ^L GNU LIBRARY GENERAL PUBLIC LICENSE
> Version 2, June 1991
>
> [... rest of the LGPLv2 text ...]
>
> I am not sure how to encode this into the _LICENSE field. Luca?
Well, the fallback for fancy licenses is "<package_name> license", as in
"bzip2 license", for example.
But in cases like this, where the license is very similar to a well-known
one, I would prefer something like "LGPLv2+ with exceptions".That is much
more informative, while still clearly stating this not equal to an LGPLv2+.
Luca
next prev parent reply other threads:[~2012-08-01 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 4:48 [Buildroot] [PATCH 1/3] poco: add license information Baruch Siach
2012-08-01 4:48 ` [Buildroot] [PATCH 2/3] mxml: " Baruch Siach
2012-08-01 18:10 ` Thomas Petazzoni
2012-08-01 20:24 ` Luca Ceresoli [this message]
2012-08-02 3:54 ` Baruch Siach
2012-08-01 4:48 ` [Buildroot] [PATCH 3/3] ebtables: " Baruch Siach
2012-08-01 18:10 ` Thomas Petazzoni
2012-08-01 18:09 ` [Buildroot] [PATCH 1/3] poco: " Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5019908D.7080205@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.