From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from [2001:67c:670:100:1d::c0] (helo=ptx.hi.pengutronix.de) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kA8Z1-0003U7-4S for ptxdist@pengutronix.de; Mon, 24 Aug 2020 11:14:51 +0200 Received: from rhi by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1kA8Z0-0008P2-RQ for ptxdist@pengutronix.de; Mon, 24 Aug 2020 11:14:50 +0200 Date: Mon, 24 Aug 2020 11:14:50 +0200 From: Roland Hieber Message-ID: <20200824091450.vbyuyg5iw2pngsro@pengutronix.de> References: <20200823134013.GA482575@lenoch> <20200823134316.GG482575@lenoch> <20200823195631.ksz5fe3635wvzmjh@pengutronix.de> <20200824082213.GA498676@lenoch> <20200824090519.mhw2hzr2fpsro436@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200824090519.mhw2hzr2fpsro436@pengutronix.de> Subject: Re: [ptxdist] [PATCH 6/7] openfortivpn: new package List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@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 . - 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