public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Luca Bocassi" <luca.boccassi@gmail.com>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3] Add new recipe for squashfs-tools-ng
Date: Fri, 23 Oct 2020 09:57:10 +0100	[thread overview]
Message-ID: <9acee59b73992f7e58c65c9c324ef28ffc528f03.camel@gmail.com> (raw)
In-Reply-To: <e5d55a34-2ec4-64d4-2d6d-8961b4bc6ba8@gmail.com>

On Thu, 2020-10-22 at 12:10 -0700, Khem Raj wrote:
> 
> On 10/22/20 4:30 AM, Luca Bocassi wrote:
> > From: Luca Boccassi <luca.boccassi@microsoft.com>
> > 
> > The main difference with squashfs-tools is the availability
> > of a shared library and a programmatic interface, rather
> > than just command-line tools.
> 
> Can you clarify which parts are under GPL-3.0+ & LGPL-3.0+ licenses.
> is it possible to ship traditional functionality from squashfs-tools 
> without using code under these licenses.

It's all defined in COPYING.md - the library is under LGPL3+, the rest
of the code (command-line tools) under GPL3+.

# License of squashfs-tools-ng

The `libsquashfs` library is released under the terms and conditions of the
**GNU Lesser General Public License version 3 or later**. This applies to
all source code in the directories `lib/sqfs`, `lib/util` and `include/sqfs`
with the following exceptions:

 - `lib/util/xxhash.c` contains a modified implementation of the xxhash32
   algorithm. See `licenses/xxhash.txt` for copyright and licensing
   information (2 clause BSD license).
 - `lib/lz4` contains files extracted from the LZ4 compression library.
   See `lib/lz4/README` for details and `licenses/LZ4.txt` for copyright and
   licensing information (2 clause BSD license).
 - `lib/zlib` contains files that have been extracted from the the zlib
   compression library and modified. See `lib/zlib/README` for details
   and `licenses/zlib.txt` for details.
 - `lib/util/hash_table.c`, `include/hash_table.h` and
   `lib/util/fast_urem_by_const.h` contain a hash table implementation (MIT
   license). See `licenses/hash_table.txt` for details.

The rest of squashfs-tools-ng is released under the terms and conditions of
the **GNU General Public License version 3 or later**.

-- 
Kind regards,
Luca Boccassi


  reply	other threads:[~2020-10-23  8:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 15:58 [PATCH] Add new recipe for squashfs-tools-ng Luca Bocassi
2020-10-21 19:02 ` [OE-core] " Richard Purdie
2020-10-22  2:21   ` Khem Raj
2020-10-22  9:13     ` Luca Bocassi
2020-10-21 19:08 ` Konrad Weihmann
2020-10-22  9:21   ` Luca Bocassi
2020-10-22  9:20 ` [PATCH v2] " Luca Bocassi
2020-10-22 11:10   ` [OE-core] " Peter Kjellerstedt
2020-10-22 11:30     ` Luca Bocassi
2020-10-22 11:30   ` [PATCH v3] " Luca Bocassi
2020-10-22 19:10     ` [OE-core] " Khem Raj
2020-10-23  8:57       ` Luca Bocassi [this message]
2020-10-24 12:58     ` Richard Purdie
2020-10-26 10:05       ` Luca Bocassi
2020-10-26 10:05     ` [PATCH v4] " Luca Bocassi
2020-10-26 10:29       ` Richard Purdie
2020-10-26 13:09         ` Luca Bocassi
2020-10-27 10:31           ` Luca Bocassi
2020-10-27 10:37           ` Richard Purdie
2020-10-27 10:59             ` Luca Bocassi
2020-10-27 11:19               ` [OE-core] " Ross Burton

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=9acee59b73992f7e58c65c9c324ef28ffc528f03.camel@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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