mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 6/7] openfortivpn: new package
Date: Mon, 24 Aug 2020 17:35:40 +0200	[thread overview]
Message-ID: <20200824153540.lvcilptzw2inz2cc@pengutronix.de> (raw)
In-Reply-To: <20200824100814.GA503263@lenoch>

On Mon, Aug 24, 2020 at 12:08:14PM +0200, Ladislav Michl wrote:
> 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:
> [...]
> > > This "unknown-exception" seems to be OpenSSL, so we get:
> > > OPENFORTIVPN_LICENSE := GPL-3.0-or-later AND OpenSSL
> > 
> > I meant the exception at the end of LICENSE:
> > 
> >     |                            Exception
> >     | 
> >     |   In addition, as a special exception, the copyright holders give permission
> >     | to link the code of portions of this program with the OpenSSL library under
> >     | certain conditions as described in each individual source file, and distribute
> >     | linked combinations including the two.
> >     | You must obey the GNU General Public License in all respects for all of the
> >     | code used other than OpenSSL.  If you modify file(s) with this exception, you
> >     | may extend this exception to your version of the file(s), but you are not
> >     | obligated to do so.  If you do not wish to do so, delete this exception
> >     | statement from your version.  If you delete this exception statement from all
> >     | source files in the program, then also delete it here.
> > 
> > This is not part of the GPL-3.0 license text, and the OpenSSL text is
> > different: <https://spdx.org/licenses/OpenSSL>
> > 
> > Putting "GPL-3.0-or-later AND OpenSSL" in SPDX syntax would mean that
> > there is code under GPL, and code under OpenSSL, which when linked
> > together would create an undistributable binary because the two licenses
> > are not compatible. But the exception here clearly allows this use case.
> > 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.
> 
> Ah, seems you already take an effort to solve this :)
> https://github.com/spdx/license-list-XML/issues/939

No, this issue was about two different exceptions. SPDX is not very
inclined to add licenses or exceptions whose wording is only used in one
single project...

 - Roland

> Ready to send v2 "WITH unknown-exception", either separately or as whole
> serie resend - I'll wait a bit more for eventual comments to show up.
>  
> > > > > +	file://src/main.c;startline=4;endline=15;md5=2d74bd9c818c4c3009c1c8782aaa23e7
> > > > 
> > > > Also there is LICENSE.OpenSSL, is this used anywhere?
> > > 
> > > Yes, I overlooked its use in two files: tunnel.c and openssl_hostname_validation.c
> > > which is ifdefed out. What about:
> > > OPENFORTIVPN_LICENSE_FILES := \
> > > 	file://LICENSE;md5=1d58d8f3da4c52035c4ad376ffabb44a \
> > > 	file://LICENSE.OpenSSL;md5=f3317a38a556060e468331158cc43fe3 \
> > > 	file://src/main.c;startline=4;endline=15;md5=2d74bd9c818c4c3009c1c8782aaa23e7 \
> > > 	file://src/tunnel.c;startline=4;endline=26;md5=5454796bf6fd04c7e4ad6bd83a627e4f
> > 
> > Yes, this looks good to me.
> > 
> > > One more question before v2: package is lacking configure script and autogen.sh
> > > is expected to be run. I solved this creating empty patch directory with symlink.
> > > Any other preferred solution?
> > 
> > The autogen.sh symlink is fine. This just happens when the distributed
> > tarballs are created automatically by git-archive. I didn't see any
> > other official tarballs either.
> > 
> >  - 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 |
> 

-- 
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 15:35 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
2020-08-24 10:08         ` Ladislav Michl
2020-08-24 15:35           ` Roland Hieber [this message]
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=20200824153540.lvcilptzw2inz2cc@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ladis@linux-mips.org \
    --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