All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Bilas <b.bilas@grinn-global.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] package/python-esptool: new package
Date: Fri, 8 Nov 2019 10:06:31 +0100	[thread overview]
Message-ID: <483e9989-ac40-cfdd-de79-78088c70ab89@grinn-global.com> (raw)
In-Reply-To: <20191108094927.49828a98@windsurf>

Hello guys,

On 08.11.2019 09:49, Thomas Petazzoni wrote:
> Hello,
>
> +Yegor in Cc.
>
> On Fri, 8 Nov 2019 09:45:50 +0100
> Bartosz Bilas <b.bilas@grinn-global.com> wrote:
>
>>>> +PYTHON_ESPTOOL_LICENSE = GNU General Public License v2 or later (GPLv2+)
>>> The proper way to describe this is just:
>>>
>>> PYTHON_ESPTOOL_LICENSE = GPL-2.0+
>> this was created using scanpypi script so do you think we should fix
>> that script or adjust that manually as you did?
> scanpipy already has a conversion table between Pipy-provided license
> strings and Buildroot license tags:
>
>                  'Apache Software License': 'Apache-2.0',
>                  'BSD License': 'FIXME: please specify the exact BSD version',
>                  'European Union Public Licence 1.0': 'EUPL-1.0',
>                  'European Union Public Licence 1.1': 'EUPL-1.1',
>                  "GNU General Public License": "GPL",
>                  "GNU General Public License v2": "GPL-2.0",
>                  "GNU General Public License v2 or later": "GPL-2.0+",
>                  "GNU General Public License v3": "GPL-3.0",
>                  "GNU General Public License v3 or later": "GPL-3.0+",
>                  "GNU Lesser General Public License v2": "LGPL-2.1",
>                  "GNU Lesser General Public License v2 or later": "LGPL-2.1+",
>                  "GNU Lesser General Public License v3": "LGPL-3.0",
>                  "GNU Lesser General Public License v3 or later": "LGPL-3.0+",
>                  "GNU Library or Lesser General Public License": "LGPL-2.0",
>                  "ISC License": "ISC",
>                  "MIT License": "MIT",
>                  "Mozilla Public License 1.0": "MPL-1.0",
>                  "Mozilla Public License 1.1": "MPL-1.1",
>                  "Mozilla Public License 2.0": "MPL-2.0",
>                  "Zope Public License": "ZPL"
>
> Obviously, the value "GNU General Public License v2 or later (GPLv2+)"
> that was used by this package didn't match any entry in this table.
> Since "GNU General Public License v2 or later (GPLv2+)" is apparently
> rarely used, I don't think it's worth adding an entry to the table: for
> such cases, we simply have to do a manual fixup. In any case,
> ./utils/scanpipy does not guarantee that it provides a fully working
> and correct Buildroot package: it extracts most information from Pipy,
> but a careful review, and possibly some changes may be necessary.

I assume that's the same for that comment bellow:

 > +config BR2_PACKAGE_PYTHON_ESPTOOL
 > +??? bool "python-esptool"
 > +??? select BR2_PACKAGE_PYTHON_SERIAL # runtime
 > +??? select BR2_PACKAGE_PYTHON_PYAES # runtime
 > +??? select BR2_PACKAGE_PYTHON_ECDSA # runtime

Alphabetic ordering.

but I think it wouldn't be difficult to handle it in the script.

Best
Bartek
>
> Best regards,
>
> Thomas

  parent reply	other threads:[~2019-11-08  9:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 17:05 [Buildroot] [PATCH v2 1/2] package/python-pyaes: new package Bartosz Bilas
2019-11-07 17:05 ` [Buildroot] [PATCH v2 2/2] package/python-esptool: " Bartosz Bilas
2019-11-07 22:50   ` Thomas Petazzoni
2019-11-08  8:45     ` Bartosz Bilas
2019-11-08  8:49       ` Thomas Petazzoni
2019-11-08  9:01         ` Yegor Yefremov
2019-11-08  9:06         ` Bartosz Bilas [this message]
2019-11-08  9:17           ` Bartosz Bilas
2019-11-08  9:21           ` Thomas Petazzoni
2019-11-07 22:50 ` [Buildroot] [PATCH v2 1/2] package/python-pyaes: " Thomas Petazzoni

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=483e9989-ac40-cfdd-de79-78088c70ab89@grinn-global.com \
    --to=b.bilas@grinn-global.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.