Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Solid-Run HummingBoard i2eX defconfig and bootable microSD Bash script
Date: Sun, 31 May 2015 07:14:12 +0300	[thread overview]
Message-ID: <20150531041412.GB2282@tarshish> (raw)
In-Reply-To: <alpine.DEB.2.11.1505290930060.2289@tanhuma.tkos.co.il>

Hi Yonatan,

On Fri, May 29, 2015 at 09:56:25AM +0300, Jonathan Ben Avraham wrote:
> On Fri, 29 May 2015, Baruch Siach wrote:
> >On Thu, May 28, 2015 at 04:36:10PM +0300, Jonathan Ben-Avraham wrote:
> >>+# @(#) Create a bootable SD card from Buildroot tree for the HummingBoard 
> >>i2eX
> >>+#
> >>+# Copyright (c) 2015 Tk Open Systems Ltd. all rights reserved
> >>+# License granted for public use under the terms of the "Attribution-ShareAlike
> >>+# 4.0 International" license, See full text at
> >>+# https://creativecommons.org/licenses/by-sa/4.0/legalcode
> >
> >Buildroot code itself is under GPLv2. See
> >http://nightly.buildroot.org/manual.html#_complying_with_the_buildroot_license.
> >Is this license GPLv2 compatible?
>
> Regarding the use of the CC SA license, it seems to me that if there are
> packages using the MIT and BSD licenses in Buildroot then the CC AS license
> should be Ok also.
> 
> If you want to claim that there is a difference between packages that are
> downloaded and contributions that are part of Buildroot itself, then I would
> say that the difference between GPLv2 and CC SA for a Bash script - which is
> not compiled and cannot be linked against, is not significant.
> 
> I prefer to use the CC licenses, because they  are simpler, clearer, and
> more appropriate to configuration files and scripts which are not compiled
> or linked against, and they avoid both the heavy RMS idealogical baggage and
> the legal confusions associated with the GPL licenses without any loss of
> rights to the public.

The fact that all of Buildroot code itself is released under GPLv2 should make 
life easier for downstream Buildroot distributors (and their legal 
departments).

Anyway, in case Buildroot maintainers agree to accept scripts under a 
different license, please add a patch to section 12.3 of the manual to clarify
Buildroot license.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-05-31  4:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 13:36 [Buildroot] [PATCH 1/1] Solid-Run HummingBoard i2eX defconfig and bootable microSD Bash script Jonathan Ben-Avraham
2015-05-29  4:40 ` Baruch Siach
2015-05-29  5:19   ` Jonathan Ben Avraham
2015-05-29  5:26   ` Jonathan Ben Avraham
2015-05-29  6:56   ` Jonathan Ben Avraham
2015-05-31  4:14     ` Baruch Siach [this message]
2015-05-31  7:06       ` Thomas Petazzoni
2015-05-31  7:51         ` Jonathan Ben Avraham
2015-05-29  7:56   ` Jonathan Ben Avraham
2015-05-31  6:25     ` Baruch Siach
2015-05-31  7:57       ` Jonathan Ben Avraham
2015-05-31  9:18         ` Baruch Siach
2015-05-31  9:37           ` Jonathan Ben Avraham

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=20150531041412.GB2282@tarshish \
    --to=baruch@tkos.co.il \
    --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