From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/2] getent: new package
Date: Mon, 18 Aug 2014 16:52:48 +0200 [thread overview]
Message-ID: <20140818165248.393a57db@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LWWdZF12uQBX487i71S8JLSqDuFf3tRtLfPhK=wbJd-Mg@mail.gmail.com>
Dear Thomas De Schampheleire,
On Mon, 18 Aug 2014 13:50:57 +0200, Thomas De Schampheleire wrote:
> How do you conclude this license?
uclibc: there is no license specific in the script itself, so by
default it's the same license as the entire project, i.e LGPLv2.1+
glibc: the header comment in nss/getent.c is clear: it's under
LGPLv2.1+.
> Isn't this dependent on the case glibc versus uclibc/musl ? Or do each
> of these use the same license?
See above :)
> Also, shouldn't we specify GETENT_LICENSE_FILES and make sure the
> appropriate license text is present?
Which license text file should be used? In neither of the uclibc/musl
or glibc cases we have access to the license text. I can include a
COPYING file in package/getent/, but that's going to be 100x times
larger than the getent script :)
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-18 14:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 9:54 [Buildroot] [PATCHv2 0/2] Installation of getent, solving bug #7142 Thomas Petazzoni
2014-08-18 9:54 ` [Buildroot] [PATCHv2 1/2] getent: new package Thomas Petazzoni
2014-08-18 11:50 ` Thomas De Schampheleire
2014-08-18 14:52 ` Thomas Petazzoni [this message]
2014-08-18 15:07 ` Thomas De Schampheleire
2014-08-18 15:33 ` Thomas Petazzoni
2014-08-18 17:18 ` Thomas De Schampheleire
2014-10-12 15:22 ` Arnout Vandecappelle
2014-10-12 16:32 ` Peter Korsgaard
2014-10-13 9:17 ` Peter Korsgaard
2014-10-13 16:34 ` Arnout Vandecappelle
2014-08-18 9:54 ` [Buildroot] [PATCHv2 2/2] ecryptfs-utils: add runtime dependency on getent Thomas Petazzoni
2014-10-12 15:23 ` Arnout Vandecappelle
2014-10-12 16:32 ` Peter Korsgaard
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=20140818165248.393a57db@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