From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] snmppp: extract license text from source files
Date: Wed, 22 Jul 2015 23:50:39 +0200 [thread overview]
Message-ID: <20150722235039.0beaf01e@free-electrons.com> (raw)
In-Reply-To: <20150722214756.GD3777@free.fr>
Hello,
On Wed, 22 Jul 2015 23:47:56 +0200, Yann E. MORIN wrote:
> In principle, yes. However, consider this case:
>
> - package is BSD-3c licensed, so redistributing the source is not
> mandatory,
>
> - the user has a local patch for that package,
>
> - the user does not want to share those modifications, which he is
> allowed to do as per the BSD-3c,
>
> - using a source file as license file would "leak" those modifications
> (or part of those) in the legal-info.
>
> So, using a source file is not perfect either.
No, it's certainly not perfect, but good enough. I would expect people
to review the legal-info generated by Buildroot before publishing them,
so they should notice such issues especially if they are really
concerned about no publishing the source code for a BSD-3c component:
by default we copy the source code for that package to legal-info
(though not the local patch).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-22 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 16:29 [Buildroot] [PATCH] snmppp: extract license text from source files Luca Ceresoli
2015-07-21 19:54 ` Thomas Petazzoni
2015-07-22 21:01 ` Yann E. MORIN
2015-07-22 21:26 ` Thomas Petazzoni
2015-07-22 21:33 ` Yann E. MORIN
2015-07-22 21:37 ` Thomas Petazzoni
2015-07-22 21:47 ` Yann E. MORIN
2015-07-22 21:50 ` 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=20150722235039.0beaf01e@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