Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/5] package/python-asttokens: new package
Date: Fri, 02 Jun 2023 21:45:01 +0200	[thread overview]
Message-ID: <87zg5hd4xu.fsf@48ers.dk> (raw)
In-Reply-To: <20230528190111.2430580-3-romain.naour@gmail.com> (Romain Naour's message of "Sun, 28 May 2023 21:01:09 +0200")

>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:

 > Signed-off-by: Romain Naour <romain.naour@gmail.com>
 > ---
 >  package/Config.in                              |  1 +
 >  package/python-asttokens/Config.in             |  7 +++++++
 >  package/python-asttokens/python-asttokens.hash |  5 +++++
 >  package/python-asttokens/python-asttokens.mk   | 16 ++++++++++++++++
 >  4 files changed, 29 insertions(+)
 >  create mode 100644 package/python-asttokens/Config.in
 >  create mode 100644 package/python-asttokens/python-asttokens.hash
 >  create mode 100644 package/python-asttokens/python-asttokens.mk

 > diff --git a/package/Config.in b/package/Config.in
 > index 3da005b5e5..e018fe66ca 100644
 > --- a/package/Config.in
 > +++ b/package/Config.in
 > @@ -966,6 +966,7 @@ menu "External python modules"
 >  	source "package/python-argon2-cffi-bindings/Config.in"
 >  	source "package/python-arrow/Config.in"
 >  	source "package/python-asgiref/Config.in"
 > +	source "package/python-asttokens/Config.in"
 >  	source "package/python-asn1crypto/Config.in"

check-package (rightly) complains that n comes before t:

package/Config.in:970: Packages in: menu "External python modules",
                       are not alphabetically ordered;
                       correct order: '-', '_', digits, capitals, lowercase;
                       first incorrect package: python-asn1crypto

Committed with that fixed, thanks.

>  	source "package/python-async-generator/Config.in"
 >  	source "package/python-async-lru/Config.in"
 > diff --git a/package/python-asttokens/Config.in b/package/python-asttokens/Config.in
 > new file mode 100644
 > index 0000000000..2732b8124b
 > --- /dev/null
 > +++ b/package/python-asttokens/Config.in
 > @@ -0,0 +1,7 @@
 > +config BR2_PACKAGE_PYTHON_ASTTOKENS
 > +	bool "python-asttokens"
 > +	select BR2_PACKAGE_PYTHON_SIX # runtime
 > +	help
 > +	  Annotate AST trees with source code positions.
 > +
 > +	  https://github.com/gristlabs/asttokens
 > diff --git a/package/python-asttokens/python-asttokens.hash b/package/python-asttokens/python-asttokens.hash
 > new file mode 100644
 > index 0000000000..6529e4db41
 > --- /dev/null
 > +++ b/package/python-asttokens/python-asttokens.hash
 > @@ -0,0 +1,5 @@
 > +# md5, sha256 from https://pypi.org/pypi/asttokens/json
 > +md5  a9ae6ae0f85398e511bcb9ec87695eed  asttokens-2.2.1.tar.gz
 > +sha256  4622110b2a6f30b77e1473affaa97e711bc2f07d3f10848420ff1898edbe94f3  asttokens-2.2.1.tar.gz
 > +# Locally computed sha256 checksums
 > +sha256  b40930bbcf80744c86c46a12bc9da056641d722716c378f5659b9e555ef833e1  LICENSE
 > diff --git a/package/python-asttokens/python-asttokens.mk b/package/python-asttokens/python-asttokens.mk
 > new file mode 100644
 > index 0000000000..8a8ce1ddd9
 > --- /dev/null
 > +++ b/package/python-asttokens/python-asttokens.mk
 > @@ -0,0 +1,16 @@
 > +################################################################################
 > +#
 > +# python-asttokens
 > +#
 > +################################################################################
 > +
 > +PYTHON_ASTTOKENS_VERSION = 2.2.1
 > +PYTHON_ASTTOKENS_SOURCE = asttokens-$(PYTHON_ASTTOKENS_VERSION).tar.gz
 > +PYTHON_ASTTOKENS_SITE = https://files.pythonhosted.org/packages/c8/e3/b0b4f32162621126fbdaba636c152c6b6baec486c99f48686e66343d638f
 > +PYTHON_ASTTOKENS_SETUP_TYPE = setuptools
 > +PYTHON_ASTTOKENS_LICENSE = Apache-2.0
 > +PYTHON_ASTTOKENS_LICENSE_FILES = LICENSE
 > +
 > +PYTHON_ASTTOKENS_DEPENDENCIES = host-python-setuptools-scm
 > +
 > +$(eval $(python-package))
 > -- 

 > 2.34.3

 > _______________________________________________
 > buildroot mailing list
 > buildroot@buildroot.org
 > https://lists.buildroot.org/mailman/listinfo/buildroot


-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-06-02 19:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-28 19:01 [Buildroot] [PATCH 1/5] package/python-executing: new package Romain Naour
2023-05-28 19:01 ` [Buildroot] [PATCH 2/5] package/python-pure-eval: " Romain Naour
2023-06-02 19:45   ` Peter Korsgaard
2023-06-14 11:40   ` Peter Korsgaard
2023-05-28 19:01 ` [Buildroot] [PATCH 3/5] package/python-asttokens: " Romain Naour
2023-06-02 19:45   ` Peter Korsgaard [this message]
2023-06-14 11:40   ` Peter Korsgaard
2023-05-28 19:01 ` [Buildroot] [PATCH 4/5] package/python-stack-data: " Romain Naour
2023-06-02 19:45   ` Peter Korsgaard
2023-06-14 11:40   ` Peter Korsgaard
2023-05-28 19:01 ` [Buildroot] [PATCH 5/5] package/ipython: add missing dependencies Romain Naour
2023-06-02 19:46   ` Peter Korsgaard
2023-06-14 11:40   ` Peter Korsgaard
2023-06-02 19:42 ` [Buildroot] [PATCH 1/5] package/python-executing: new package Peter Korsgaard
2023-06-14 11:40 ` Peter Korsgaard

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=87zg5hd4xu.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    /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