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] [RFC PATCH 1/2] scancpan: support more licenses
Date: Mon, 13 Aug 2018 23:16:59 +0200	[thread overview]
Message-ID: <20180813211659.GG7915@scaer> (raw)
In-Reply-To: <CALURroRRC9sPBLeAuv4=0XOwgGvnEZchKU03xxPtgn0Uheik3Q@mail.gmail.com>

Christopher, All,

On 2018-08-13 10:35 -0700, Christopher McCrory spake thusly:
> On Mon, Aug 13, 2018 at 9:54 AM, Thomas Petazzoni < [1]thomas.petazzoni@bootlin.com> wrote:
>   > +? ? ? ? $license =~ s|lgpl|LGPL-2.1|;
>   Just "lgpl" always means it's LGPL-2.1 ?
> Apparently

IANAL...

Usually, if any license of the GPL familly is used without any version
specified, then it means just any version can be used:

    https://www.gnu.org/licenses/gpl.html

    14. Revised Versions of this License.

    [...]  If the Program does not specify a version number of the GNU
    General Public License, you may choose any version ever published
    by the Free Software Foundation.

Similar clauses can be had for each license. So I doubt 'lgpl' would
stand for LGPL-2.1.

Besides, see below...

>   > +? ? ? ? $license =~ s|bsd|BSD|;
>   "BSD" is not a license. There are several different BSD licenses.
>   Though with just "bsd" as an initial information, there's not much you
>   can do :-/
> 
> yea :(
> AFAICT, this is the source from Base.pm

What 'Base.pm' are you talink about? On my Ubuntu 17.10, I get:

    $ apt-file search /Base.pm |wc -l
    191

> ? my %licenses = (
> ??? perl???????? => 'Perl_5',
> ??? apache?????? => 'Apache_2_0',
> ??? apache_1_1?? => 'Apache_1_1',
> ??? artistic???? => 'Artistic_1',
> ??? artistic_2?? => 'Artistic_2',
> ??? lgpl???????? => 'LGPL_2_1',
> ??? lgpl2??????? => 'LGPL_2_1',
> ??? lgpl3??????? => 'LGPL_3_0',
> ??? bsd????????? => 'BSD',
> ??? gpl????????? => 'GPL_1',
> ??? gpl2???????? => 'GPL_2',
> ??? gpl3???????? => 'GPL_3',
> ??? mit????????? => 'MIT',
> ??? mozilla????? => 'Mozilla_1_1',
> ??? restrictive? => 'Restricted',
> ??? open_source? => undef,
> ??? unrestricted => undef,
> ??? unknown????? => undef,
> ? );
> 
> ?# TODO - would be nice to not have these here, since they're more
> ? # properly stored only in Software::License
> ? my %license_urls = (
> ??? perl???????? => 'http://dev.perl.org/licenses/',
> ??? apache?????? => 'http://apache.org/licenses/LICENSE-2.0',
> ??? apache_1_1?? => 'http://apache.org/licenses/LICENSE-1.1',
> ??? artistic???? => 'http://opensource.org/licenses/artistic-license.php',
> ??? artistic_2?? => 'http://opensource.org/licenses/artistic-license-2.0.php',
> ??? lgpl???????? => 'http://opensource.org/licenses/lgpl-license.php',
> ??? lgpl2??????? => 'http://opensource.org/licenses/lgpl-2.1.php',
> ??? lgpl3??????? => 'http://opensource.org/licenses/lgpl-3.0.html',
> ??? bsd????????? => 'http://opensource.org/licenses/bsd-license.php',
> ??? gpl????????? => 'http://opensource.org/licenses/gpl-license.php',
> ??? gpl2???????? => 'http://opensource.org/licenses/gpl-2.0.php',
> ??? gpl3???????? => 'http://opensource.org/licenses/gpl-3.0.html',
> ??? mit????????? => 'http://opensource.org/licenses/mit-license.php',
> ??? mozilla????? => 'http://opensource.org/licenses/mozilla1.1.php',
> ??? restrictive? => undef,
> ??? open_source? => undef,
> ??? unrestricted => undef,
> ??? unknown????? => undef,
> ? );

And at the same time, still on my Ubuntu 17.10, I was looking at
/usr/share/perl/5.26.0/CPAN/Meta/Converter.pm, which has;

    # The "old" values were defined by Module::Build, and were often vague.
    # I have
    # made the decisions below based on reading Module::Build::API and how
    # clearly
    # it specifies the version of the license.
    my %license_map_2 = (
      (map { $_ => $_ } @valid_licenses_2),
      apache      => 'apache_2_0',  # clearly stated as 2.0
      artistic    => 'artistic_1',  # clearly stated as 1
      artistic2   => 'artistic_2',  # clearly stated as 2
      gpl         => 'open_source', # we don't know which GPL; punt
      lgpl        => 'open_source', # we don't know which LGPL; punt
      mozilla     => 'open_source', # we don't know which MPL; punt
      perl        => 'perl_5',      # clearly Perl 5
      restrictive => 'restricted',
    );

So... The resolution is not that clear-cut IMNSHO...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-08-13 21:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 13:11 [Buildroot] [RFC PATCH 0/2] scancpan patches Christopher McCrory
2018-08-13 13:11 ` [Buildroot] [RFC PATCH 1/2] scancpan: support more licenses Christopher McCrory
2018-08-13 15:42   ` François Perrad
2018-08-13 16:54   ` Thomas Petazzoni
2018-08-13 17:35     ` Christopher McCrory
2018-08-13 21:16       ` Yann E. MORIN [this message]
2018-08-13 22:52         ` Arnout Vandecappelle
2018-08-14 11:33   ` Thomas Petazzoni
2018-08-15 11:57     ` Christopher McCrory
2018-08-13 13:11 ` [Buildroot] [RFC PATCH 2/2] scancpan: wrap abstract if too long Christopher McCrory
2018-08-13 16:29   ` François Perrad
2018-08-16  3:07   ` Ricardo Martincoski

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=20180813211659.GG7915@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