public inbox for
 help / color / mirror / Atom feed
From: Randy MacLeod <>
To: <>
Subject: bzip2-testing LICENSE
Date: Tue, 26 May 2020 16:35:30 -0400	[thread overview]
Message-ID: <> (raw)


I've been reviewing the work that Rahul has done to package
bzip2-testing for Yocto / Open Embedded. One question that I have
is about the license terms of the repo. In brief it seems
that the COPYING/LICENSE files are left over from the original
projects and that it's possible that since the remaining
files are data rather than source, that the LICENSE terms no longer
apply. For a more details explanation, see:,,,20,0,0,0::Created,,bzip2+test+suite,20,2,0,73224911

My conclusion is that the bzip2-ptest yocto package should be
tagged with just:
    LICENSE = "GPLv3+"
due to the terms of the top level script rather
that the alternative:
    LICENSE = \
    "bzip2-1.0.6 & GPLv3+ & Apache-2.0 & MS-PL & BSD-3-Clause & Zlib"

If you agree, then I'd be happy to send a commit to remove
the license files in the sub-directories and include a nice long
explanation in the commit log based on the email referenced above.
If not that's certainly fine as well but I would be puzzled by such a 
result! :)

Note that Yocto users typically automatically fetch the source at
build time from the original SRC_URI so this certainly doesn't
affect distribution of the bzip2-test source.

Thanks for your attention ,

# Randy MacLeod
# Wind River Linux

             reply	other threads:[~2020-05-26 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 20:35 Randy MacLeod [this message]
2020-05-26 21:28 ` Mark Wielaard
2020-06-02 13:57   ` Randy MacLeod

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).