From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] package/physfs: new package
Date: Sun, 5 Mar 2017 22:37:49 +0100 [thread overview]
Message-ID: <20170305223749.3567d0af@free-electrons.com> (raw)
In-Reply-To: <755ee979-57de-4718-9fa0-5f7de1f05289@gmail.com>
Hello,
On Sun, 5 Mar 2017 22:14:02 +0100, Romain Naour wrote:
> > zlib license (physfs), LGPv2.1+ or CPL or special license (lzma)
> >
> > ?
>
> It seems some files are under public domain when the special license is used.
>
> SPECIAL EXCEPTION #3: Igor Pavlov, as the author of this code, expressly permits
> you to use code of the following files:
> BranchTypes.h, LzmaTypes.h, LzmaTest.c, LzmaStateTest.c, LzmaAlone.cpp,
> LzmaAlone.cs, LzmaAlone.java
> as public domain code.
>
> Maybe "special license" is enough ?
My understanding of lzma.txt is that you really have the choice between
those different licensing options, so I believe encoding all of them in
<pkg>_LICENSE is probably better.
Cc'ing Arnout and Yann to get their insight.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-05 21:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 22:56 [Buildroot] [PATCH v3 1/2] package/physfs: new package Romain Naour
2017-03-01 22:56 ` [Buildroot] [PATCH v3 2/2] package/supertux: " Romain Naour
2017-03-05 15:52 ` [Buildroot] [PATCH v3 1/2] package/physfs: " Romain Naour
2017-03-05 20:51 ` Thomas Petazzoni
2017-03-05 21:14 ` Romain Naour
2017-03-05 21:37 ` Thomas Petazzoni [this message]
2017-03-05 22:06 ` Arnout Vandecappelle
2017-03-05 22:13 ` Romain Naour
2017-03-05 23:31 ` Arnout Vandecappelle
2017-03-06 20:32 ` Romain Naour
2017-03-05 22:41 ` Thomas Petazzoni
2017-03-05 23:34 ` Arnout Vandecappelle
2017-03-06 21:43 ` Yann E. MORIN
2017-03-07 8:31 ` Arnout Vandecappelle
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=20170305223749.3567d0af@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox