Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 17/17] perl-termreadkey: new package
Date: Tue, 14 Aug 2018 17:53:37 +0200	[thread overview]
Message-ID: <20180814155337.GM7915@scaer> (raw)
In-Reply-To: <20180813235716.070f77f0@windsurf>

Thomas, Christopher, All,

On 2018-08-13 23:57 +0200, Thomas Petazzoni spake thusly:
> Adding Yann and Arnout, licensing question below.
> On Sat, 11 Aug 2018 11:27:49 -0700, Christopher McCrory wrote:
> > +PERL_TERMREADKEY_VERSION = 2.37
> > +PERL_TERMREADKEY_SOURCE = TermReadKey-$(PERL_TERMREADKEY_VERSION).tar.gz
> > +PERL_TERMREADKEY_SITE = $(BR2_CPAN_MIRROR)/authors/id/J/JS/JSTOWE
> > +PERL_TERMREADKEY_LICENSE = Artistic or GPL-1.0+
> 
> This is not correct I believe.

IANAL...

Indeed it's not.

> The README file says this:
> 
> """
>  Term::ReadKey 2.36 - Change terminal modes, and perform non-blocking reads.
> 
>  Copyright (C) 1994-1999 Kenneth Albanowski.
>                2001-2016 Jonathan Stowe and others
> 
> This package is dual licensed.  You can either choose to license it under
> the original terms which were:
> 
>  Unlimited distribution and/or modification is allowed as long as this
>  copyright notice remains intact.
> 
> Or the standard Perl terms:
> 
>   This module is free software; you can redistribute it and/or modify it
>   under the terms of the Artistic License. For details, see the full
>   text of the license in the file "Artistic" that should have been provided
>   with the version of perl you are using.
> 
>   This program is distributed in the hope that it will be useful, but
>   without any warranty; without even the implied warranty of merchantability
>   or fitness for a particular purpose.
> """
> 
> So it is not under "Artistic or GPL-1.0+", but it is under "Artistic or
> <some funky license>".
> 
> According to
> http://docs.activestate.com/activeperl/5.22/perl/lib/Term/ReadKey.html,
> the small "Unlimited distribution..." license was the only license of
> this Perl module up to version 2.31, at which point the Artistic
> license was added as an option.
> 
> I don't know how to SPDX-encode this weird license. Perhaps we should
> simply not care, and say the license is just "Artistic" ? Yann ?
> Arnout ?

According to the SPDX FAQ [0]:

  * How does one handle [...] licenses not found in the SPDX License
    List?

    [...] one can add the license text to the SPDX file and define a new
    license label. That license identifier is defined only for that
    specific SPDX document. This is explained in Section 6 of the SPDX
    Specification or see [1].

However, we do not have our own SPDX document in Buildroot, so section 6
does not apply.

However, we already have similar situations, where we simply state
something like:

    FOO_LICENSE = Foo license

So, I would state something similar here:

    PERL_TERMREADKEY_LICENSE = Term::ReadKey license or Artistic-1.0-Perl

Please double-check which versiopn of the Artistic license this is
refering to (i.e. the docs says "see the full text of the license in the
file "Artistic" that should have been provided with the version of perl
you are using.", so I just used Artistic-1.0-Perl but I'm not sure...)

Regards,
Yann E. MORIN.

[0] https://spdx.org/frequently-asked-questions-faq-0
[1] https://spdx.org/spdx-specification-21-web-version#h.1v1yuxt

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2018-08-14 15:53 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-11 18:27 [Buildroot] [PATCH 00/17] even more perl modules Christopher McCrory
2018-08-11 18:27 ` [Buildroot] [PATCH 01/17] perl-cgi: add host Christopher McCrory
2018-08-12 12:11   ` Thomas Petazzoni
2018-08-13 13:23     ` Christopher McCrory
2018-08-11 18:27 ` [Buildroot] [PATCH 02/17] perl-html-parser: " Christopher McCrory
2018-08-11 18:27 ` [Buildroot] [PATCH 03/17] perl-html-tagset: " Christopher McCrory
2018-08-11 18:27 ` [Buildroot] [PATCH 04/17] perl-class-std-fast: new package Christopher McCrory
2018-08-12 16:45   ` François Perrad
2018-08-12 21:17   ` Thomas Petazzoni
2018-08-12 21:18     ` Thomas Petazzoni
2018-08-13 11:21   ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 05/17] perl-data-optlist: " Christopher McCrory
2018-08-12 16:46   ` François Perrad
2018-08-13 11:21   ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 06/17] perl-module-runtime: add host Christopher McCrory
2018-08-12  9:21   ` François Perrad
2018-08-12 12:13     ` Thomas Petazzoni
2018-08-13 21:59       ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 07/17] perl-dist-checkconflicts: new package Christopher McCrory
2018-08-14  3:59   ` François Perrad
2018-08-11 18:27 ` [Buildroot] [PATCH 08/17] perl-io-socket-multicast: " Christopher McCrory
2018-08-12 16:48   ` François Perrad
2018-08-13 12:16   ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 09/17] perl-mime-tools: " Christopher McCrory
2018-08-12 16:49   ` François Perrad
2018-08-13 12:16   ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 10/17] perl-module-implementation: " Christopher McCrory
2018-08-12 16:50   ` François Perrad
2018-08-13 21:31   ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 11/17] perl-package-stash: " Christopher McCrory
2018-08-11 19:37   ` François Perrad
2018-08-11 21:31     ` Christopher McCrory
2018-08-13 21:31       ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 12/17] perl-template-toolkit: " Christopher McCrory
2018-08-12  8:04   ` François Perrad
2018-08-13 21:33     ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 13/17] perl-time-parsedate: " Christopher McCrory
2018-08-12 16:51   ` François Perrad
2018-08-13 21:46   ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 14/17] perl-x10: " Christopher McCrory
2018-08-12 16:52   ` François Perrad
2018-08-13 21:49   ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 15/17] perl-module-build: add target Christopher McCrory
2018-08-12  8:07   ` François Perrad
2018-08-13 21:34     ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 16/17] perl-class-load: new package Christopher McCrory
2018-08-12 16:57   ` François Perrad
2018-08-13 21:35     ` Thomas Petazzoni
2018-08-11 18:27 ` [Buildroot] [PATCH 17/17] perl-termreadkey: " Christopher McCrory
2018-08-12 16:55   ` François Perrad
2018-08-13 21:57   ` Thomas Petazzoni
2018-08-13 22:40     ` Arnout Vandecappelle
2018-08-14 15:53     ` Yann E. MORIN [this message]
2018-08-15 11:24       ` Christopher McCrory
2018-08-15 16:23         ` Yann E. MORIN

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=20180814155337.GM7915@scaer \
    --to=yann.morin.1998@free.fr \
    --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