From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-daemon: bump to version 2.1.1
Date: Sun, 18 Sep 2016 16:20:43 +0200 [thread overview]
Message-ID: <20160918162043.290611ff@free-electrons.com> (raw)
In-Reply-To: <1474165881-2553-1-git-send-email-danomimanchego123@gmail.com>
Hello,
On Sat, 17 Sep 2016 22:31:21 -0400, Danomi Manchego wrote:
> Bump to the latest version, to get python3 support.
>
> Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com>
I've applied, thanks!
> NOTE: It is not quite as clear to me in this version that the GPLv3
> license is only test code and build code, because there are more
> hits for "gpl" when I grep the package, in setup.py, version.py,
> test_version.py, the egg info SOURCES.txt, and a few more. However,
> the package home page at https://pypi.python.org/pypi/python-daemon/
> indicates Apache-2 only, as opposed to the previous PSF license. The
> doc/FAQ also mentions only Apache-2. So I am taking them at their word.
I've looking into it a bit, and I believe you're right. For the sake of
correctness, I've just changed it to:
PYTHON_DAEMON_LICENSE = Apache-2.0 (library), GPLv3+ (test, build)
so that we're clear that the build aspect (i.e setup.py) is under
GPLv3+ as well. But anyway, what really matters is what gets installed,
i.e the library itself.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-18 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 2:31 [Buildroot] [PATCH 1/1] python-daemon: bump to version 2.1.1 Danomi Manchego
2016-09-18 14:20 ` Thomas Petazzoni [this message]
2016-09-21 5:31 ` Thomas Petazzoni
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=20160918162043.290611ff@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