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:05:04 +0200 [thread overview]
Message-ID: <20161015120504.2e88e2f7@free-electrons.com> (raw)
In-Reply-To: <874m4eosfn.fsf@dell.be.48ers.dk>
Hello,
On Sat, 15 Oct 2016 11:46:52 +0200, Peter Korsgaard wrote:
> > - With the release of BIND 9.11.0, ISC is changing the open source
> > license for BIND from the ISC license to the Mozilla Public License
> > (MPL 2.0). See release notes:
> > http://ftp.isc.org/isc/bind9/9.11.0/RELEASE-NOTES-bind-9.11.0.html
>
> > - Explicitly enable/disable zlib support, otherwise the configure script
> > will fail like this:
>
> > checking for zlib library... yes
> > checking for library containing deflate... no
> > configure: error: found zlib include but not library.
>
> Committed, thanks.
Sorry I forgot to say it on the mailing list, but the license change is
a bit weird. Indeed, there is still a COPYRIGHT file which contains the
old license text. And this file is the one still referenced by the
LICENSE_FILES variable.
Then, there is a new file, called LICENSE, which really contains the
MPL 2.0 license text.
So:
1/ The LICENSE_FILES variable is now wrong.
2/ Upstream is very confusing with those two license files, and we
should probably report that to them. It currently makes it very
unclear if everything is under MPL2.0 or not.
Best regards,
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:05 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 [this message]
2016-10-15 10:28 ` Vicente Olivert Riera
2016-10-15 10:40 ` Thomas Petazzoni
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=20161015120504.2e88e2f7@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