All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] package/physfs: new package
Date: Mon, 6 Mar 2017 00:31:14 +0100	[thread overview]
Message-ID: <3f6177f1-6dd4-119c-e6a1-fadc9faf483a@mind.be> (raw)
In-Reply-To: <b370e822-a293-56ec-f151-69882e8b1786@gmail.com>



On 05-03-17 23:13, Romain Naour wrote:
> Hi Arnout, all,
> 
> Le 05/03/2017 ? 23:06, Arnout Vandecappelle a ?crit :
>>
>>
>> On 05-03-17 22:37, Thomas Petazzoni wrote:
>>> 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.
>>
>>  I was just about to reply :-)
>>
>>  First of all, I don't see any 'or later' language, so it's LGPL2.1 (the version
>> mentioned in src/lzma/LGPL.txt).
> 
> Try with "any later version"

 Still don't see it, except in LGPL.txt where they explain that the library
should specify "any later version" if they want it to apply to a later version.

 Regards,
 Arnout

> 
>>
>>  I think the special cases are not interesting enough to warrant mentioning - we
>> should consider the LICENSE as a strong hint, not as a definitive assertion (it
>> is not entirely accurate in most packages). In addition, the CPL.html file which
>> is supposed to be there, is missing. The top-level README also says "It uses the
>> LGPL license, with exceptions for closed-source programs." This leads me to
>> conclude that the physfs authors, when redistributint lzma, have decided to do
>> so under LGPL and to drop the other license options.
>>
>>  So I'd say:
>>
>> PHYSFS_LICENSE = zlib license (physfs), LGPLv2.1 with exceptions (lzma)
>> PHYSFS_LICENSE_FILES = LICENSE.txt src/lzma/lzma.txt src/lzma/LGPL.txt
> 
> Ok, thanks for the help!
> 
> Best regards,
> Romain
> 
>>
>>
>>  Regards,
>>  Arnout
>>
>>
> 

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2017-03-05 23:31 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
2017-03-05 22:06         ` Arnout Vandecappelle
2017-03-05 22:13           ` Romain Naour
2017-03-05 23:31             ` Arnout Vandecappelle [this message]
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=3f6177f1-6dd4-119c-e6a1-fadc9faf483a@mind.be \
    --to=arnout@mind.be \
    --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.