Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 21:51:37 +0100	[thread overview]
Message-ID: <20170305215137.1600833e@free-electrons.com> (raw)
In-Reply-To: <4328635a-2687-59f6-a192-4af579aafb58@gmail.com>

Hello,

On Sun, 5 Mar 2017 16:52:48 +0100, Romain Naour wrote:

> PHYSFS_LICENSE = zlib license (physfs), LGPLv2.1+ (lzma)

This is not completely correct. Read src/lzma/lzma.txt for details (and
include it in the license files). The lzma SDK is available under the
following licenses:

1) GNU Lesser General Public License (GNU LGPL)
2) Common Public License (CPL)
3) Simplified license for unmodified code (read SPECIAL EXCEPTION) 
4) Proprietary license 

So perhaps:

zlib license (physfs), LGPv2.1+ or CPL or special license (lzma)

 ?

Could you respin after double checking this?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-05 20:51 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 [this message]
2017-03-05 21:14     ` Romain Naour
2017-03-05 21:37       ` Thomas Petazzoni
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=20170305215137.1600833e@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