From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bind: bump version to 9.11.0
Date: Sat, 15 Oct 2016 12:40:45 +0200 [thread overview]
Message-ID: <20161015124045.74b4eddc@free-electrons.com> (raw)
In-Reply-To: <7938ab33-1e87-7374-35a0-7d5f4bf04072@imgtec.com>
Hello,
On Sat, 15 Oct 2016 12:28:53 +0200, Vicente Olivert Riera wrote:
> that COPYRIGHT file doesn't contain the old license text. It has been
> updated since 9.10.4-P3 (previous version), and now it contains a text
> that specifies the license is MPL 2.0:
>
> --------------
> $ ~/bind-9.11.0 $ head -n5 COPYRIGHT
>
> Copyright (C) 1996-2016 Internet Systems Consortium, Inc. ("ISC")
>
> This Source Code Form is subject to the terms of the Mozilla Public
> License, v. 2.0. If a copy of the MPL was not distributed with this
> file, You can obtain one at http://mozilla.org/MPL/2.0/.
> --------------
>
> Isn't that enough?
Ah, right, I got confused by the string "ISC", which is also the name
of a license, but here is the name of the organization.
*However*, if you read this file, you see that parts of bind are not
under MPL 2.0, but instead under some other BSD-like licenses, the
OpenSSL license, etc. Shouldn't we take these into account as well ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-15 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 12:54 [Buildroot] [PATCH] bind: bump version to 9.11.0 Vicente Olivert Riera
2016-10-15 9:46 ` Peter Korsgaard
2016-10-15 10:05 ` Thomas Petazzoni
2016-10-15 10:28 ` Vicente Olivert Riera
2016-10-15 10:40 ` Thomas Petazzoni [this message]
2016-10-15 10:42 ` Vicente Olivert Riera
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=20161015124045.74b4eddc@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