From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] systemd: fix license according to README file
Date: Tue, 30 Jun 2015 22:47:56 +0200 [thread overview]
Message-ID: <20150630224756.47788250@free-electrons.com> (raw)
In-Reply-To: <1435696938-19587-1-git-send-email-Vincent.Riera@imgtec.com>
Vicente,
On Tue, 30 Jun 2015 22:42:18 +0200, Vicente Olivert Riera wrote:
> diff --git a/package/systemd/systemd.mk b/package/systemd/systemd.mk
> index ee17bc8..7094b98 100644
> --- a/package/systemd/systemd.mk
> +++ b/package/systemd/systemd.mk
> @@ -7,8 +7,8 @@
> SYSTEMD_VERSION = 221
> SYSTEMD_SITE = http://www.freedesktop.org/software/systemd
> SYSTEMD_SOURCE = systemd-$(SYSTEMD_VERSION).tar.xz
> -SYSTEMD_LICENSE = LGPLv2.1+; GPLv2+ for udev; MIT-like license for few source files listed in README
> -SYSTEMD_LICENSE_FILES = LICENSE.GPL2 LICENSE.LGPL2.1 LICENSE.MIT
> +SYSTEMD_LICENSE = LGPLv2.1+; GPLv2 and GPLv2+ for udev; Public Domain license for few source files listed in README
Why specify both GPLv2 and GPLv2+ for udev?
Also, this string really doesn't look like what we usually do, it
should rather be:
LGPLv2.1+, GPLv2+ (udev), Public Domain (few source files, see README)
and since the README is important to licensing apparently, it should be mentioned in:
> +SYSTEMD_LICENSE_FILES = LICENSE.GPL2 LICENSE.LGPL2.1
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-06-30 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 20:42 [Buildroot] [PATCH] systemd: fix license according to README file Vicente Olivert Riera
2015-06-30 20:47 ` Thomas Petazzoni [this message]
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=20150630224756.47788250@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