DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Alexander Dahl <ada@thorsis.com>
Cc: distrokit@pengutronix.de, Roland Hieber <rhi@pengutronix.de>
Subject: Re: [DistroKit] [PATCH] add GPL-2.0-only as a project license
Date: Wed, 11 Dec 2019 09:56:29 +0100	[thread overview]
Message-ID: <20191211085629.gkesfwcflea2z4tr@pengutronix.de> (raw)
In-Reply-To: <20191211074702.fqhwe3birzfgzon6@pengutronix.de>

Hi,

On Wed, Dec 11, 2019 at 08:47:02AM +0100, Robert Schwebel wrote:
> On Wed, Dec 11, 2019 at 08:41:07AM +0100, Alexander Dahl wrote:
> > so DistroKit itself is GPLv2 only. What would that mean for my BSP if I used 
> > DistroKit as a pxtdist base layer?
> 
> In fact, that's something we'll have to take care about - that's an
> explicitly intended usecase.
> 
> Stay tuned, we'll discuss how to solve this.

I thought about it a bit more, and the solution is easy: ptxdist itself
is of course GPLv2-only as well, and so is DistroKit and your own BSP.

The ptxdist license has a clarification in its COPYING file (since at least
2003, which is the begin of the git history):

  This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.

  Note: PTXdist is a build system which generates a distribution for
  embedded systems. This license does only cover the build system itself
  and doesn't affect the license of managed software in any way, even if
  it might be distributed together with the build system.

  Robert Schwebel <r.schwebel@pengutronix.de>

The clarification was modelled after the equivalent in the Linux kernel
(clarification that userspace using syscalls is intended use, not derivation)
at that time, which has nowadays been SPDXified as well:
https://github.com/torvalds/linux/blob/master/COPYING

You can put whatever proprietary applications you want to put into your BSP
without being affected by the GPL that way, and it is GPLv2, not v3, so there
are no restrictions for things like trusted boot. So I think putting DistroKit
under GPLv2 is no restriction to what we already have.

We should try to find a similar solution as the kernel's.

rsc
-- 
Pengutronix e.K.                           | Dipl.-Ing. Robert Schwebel  |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de

  reply	other threads:[~2019-12-11  8:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 14:28 Roland Hieber
2019-12-04 14:29 ` Roland Hieber
2019-12-10 12:35 ` Robert Schwebel
2019-12-11  7:41 ` Alexander Dahl
2019-12-11  7:47   ` Robert Schwebel
2019-12-11  8:56     ` Robert Schwebel [this message]
2019-12-11 11:14       ` Roland Hieber
2020-05-10 16:43         ` [DistroKit] [PATCH v2] " Roland Hieber
2020-05-23 16:03           ` Roland Hieber
2020-07-15 14:27             ` Robert Schwebel
2020-07-15 14:30               ` Robert Schwebel
2020-07-16  9:38                 ` Roland Hieber

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=20191211085629.gkesfwcflea2z4tr@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=ada@thorsis.com \
    --cc=distrokit@pengutronix.de \
    --cc=rhi@pengutronix.de \
    /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