[Buildroot] custom extraction and libs11n
Luca Ceresoli
luca at lucaceresoli.net
Wed Jul 24 21:58:24 UTC 2013
Thomas De Schampheleire <patrickdepinguin+buildroot at gmail.com> wrote:
>Hi Lee Jenkins,
...
>>
>> LIBS11N_LICENSE = Public Domain
>
>There should also be a
>LIBS11N_LICENSE_FILES = LICENSE.libs11n
>line that refers to the file describing the license.
>
>*Luca*: different files in this package fall under different licenses.
>What is the best way to handle this?
I can't check right now, but IIRC the convention in BR is a comma-separated list, e.g.:
FOO_LICENSE = LGPLv3+, BSD-3c, MIT[, another_license...]
>From the LICENSE.libs11n file:
>
>---------
>All build-related files are Public Domain.
>
>Some source code falls under other licenses such as LGPL or BSD, as
>described in their source files. To the best of my understanding, s11n
>falls under Section 5 of the LGPL, and need not be released under that
>license. (More specifically, it contains no LGPL code, but uses
>features
>provided by a couple of LGPL'd classes.)
I am not a lawyer, but I find section 5 a bit unclear.
In all cases I think that if there are LGPL files in this lib, then [part of] the lib falls under the LGPL.
But this is not a BR issue. You may want to contact the package author for a clarification.
>
>The list of files which are known to be exceptions to the Public
>Domain license:
>
>LGPL:
> lib/toolbox/bzstream.{h,cpp}
> lib/toolbox/gzstream.{h,cpp}
>
>BSD:
> include/FlexLexer.h
>
>MIT:
> lib/expat (may or may not be in your s11n distribution)
>
>Unspecified:
> toc/bin/mkdeps.c
>
>These are all released under fairly non-restritive licenses.
>
>There *may* be other such files: please see the individual source
>files if in doubt.
>-------------------
>
>
Luca
More information about the buildroot
mailing list