mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 6/7] openfortivpn: new package
Date: Mon, 24 Aug 2020 11:14:50 +0200	[thread overview]
Message-ID: <20200824091450.vbyuyg5iw2pngsro@pengutronix.de> (raw)
In-Reply-To: <20200824090519.mhw2hzr2fpsro436@pengutronix.de>

On Mon, Aug 24, 2020 at 11:05:20AM +0200, Roland Hieber wrote:
> On Mon, Aug 24, 2020 at 10:22:13AM +0200, Ladislav Michl wrote:
> So I would classify it as an exception to the GPL-3.0, but since there
> is no SPDX identifier for that exact wording yet, we can use "WITH
> unknown-exception" as a placeholder, so any users who need to collect
> licensing information will stumble upon it and are forced to investigate
> further.

As a side note: the "true" SPDX way to express this would be to create a
separate SPDX document for the unknown exception, and with that document
assign a local identifier to it, like "LicenseRef-openfortivpn-OpenSSL-
exception". Then the full license identifier can be "OpenSSL AND
"GPL-3.0-or-later WITH LicenseRef-openfortivpn-OpenSSL-exception".  But
we have no way of representing this workflow in PTXdist, since we're
only using the already existing SPDX license identifiers.

For background info, there was some discussion about this in
<https://github.com/spdx/license-list-XML/issues/939>.

 - Roland

-- 
Roland Hieber, Pengutronix e.K.          | r.hieber@pengutronix.de     |
Steuerwalder Str. 21                     | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686         | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2020-08-24  9:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 13:40 [ptxdist] [PATCH 0/7] NetworkManager stack update Ladislav Michl
2020-08-23 13:40 ` [ptxdist] [PATCH 1/7] libmbim: version bump 1.18.2 -> 1.24.2 Ladislav Michl
2020-10-06  8:18   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-08-23 13:41 ` [ptxdist] [PATCH 2/7] libqmi: version bump 1.24.4 -> 1.26.2 Ladislav Michl
2020-08-30 21:37   ` [ptxdist] [PATCH v2 " Ladislav Michl
2020-10-06  8:18     ` [ptxdist] [APPLIED] " Michael Olbrich
2020-08-23 13:41 ` [ptxdist] [PATCH 3/7] modemmanager: version bump 1.12.6 -> 1.14.2 Ladislav Michl
2020-10-06  8:18   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-08-23 13:42 ` [ptxdist] [PATCH 4/7] networkmanager: version bump 1.26.0 -> 1.26.2 Ladislav Michl
2020-10-06  8:18   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-08-23 13:42 ` [ptxdist] [PATCH 5/7] networkmanager-openvpn: version bump 1.8.4 -> 1.8.12 Ladislav Michl
2020-08-28 10:49   ` Michael Olbrich
2020-08-28 14:59     ` [ptxdist] [PATCH v2 " Ladislav Michl
2020-10-06  8:18       ` [ptxdist] [APPLIED] " Michael Olbrich
2020-08-23 13:43 ` [ptxdist] [PATCH 6/7] openfortivpn: new package Ladislav Michl
2020-08-23 19:56   ` Roland Hieber
2020-08-24  8:22     ` Ladislav Michl
2020-08-24  9:05       ` Roland Hieber
2020-08-24  9:14         ` Roland Hieber [this message]
2020-08-24 10:08         ` Ladislav Michl
2020-08-24 15:35           ` Roland Hieber
2020-08-25  7:40         ` [ptxdist] [PATCH v2 " Ladislav Michl
2020-08-25 11:04           ` Roland Hieber
2020-08-25 13:14             ` [ptxdist] [PATCH v3 " Ladislav Michl
2020-08-28 12:45   ` [ptxdist] [PATCH " Michael Olbrich
2020-08-28 14:57     ` [ptxdist] [PATCH v4 " Ladislav Michl
2020-10-06  8:18       ` [ptxdist] [APPLIED] " Michael Olbrich
2020-08-23 13:43 ` [ptxdist] [PATCH 7/7] networkmanager-fortisslvpn: " Ladislav Michl
2020-10-06  8:18   ` [ptxdist] [APPLIED] " Michael Olbrich

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=20200824091450.vbyuyg5iw2pngsro@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@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