From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-asyncssh: new package
Date: Mon, 25 Dec 2023 11:29:34 +0100 [thread overview]
Message-ID: <20231225112934.237a2b76@windsurf> (raw)
In-Reply-To: <20231214175310.207294-1-james.hilliard1@gmail.com>
Hello James,
On Thu, 14 Dec 2023 10:53:10 -0700
James Hilliard <james.hilliard1@gmail.com> wrote:
> +PYTHON_ASYNCSSH_VERSION = 2.14.1
> +PYTHON_ASYNCSSH_SOURCE = asyncssh-$(PYTHON_ASYNCSSH_VERSION).tar.gz
> +PYTHON_ASYNCSSH_SITE = https://files.pythonhosted.org/packages/5f/86/59278fefc49ddcc10567e52a8e0e1553fc936584e241d516b5682d55ea17
> +PYTHON_ASYNCSSH_SETUP_TYPE = setuptools
> +PYTHON_ASYNCSSH_LICENSE = EPL-2.0
> +PYTHON_ASYNCSSH_LICENSE_FILES = LICENSE
The COPYRIGHT file says the license is EPL-2.0 or GPL-2.0+, so I've
changed it to that, and added the COPYRIGHT file to the list of license
files, and I've applied.
One thing that would be nice for new Python packages would be to add a
runtime tests. These are relatively easy to add, and allow to verify
that all runtime dependencies are probably taken into account.
Thanks a lot for this contribution!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-25 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 17:53 [Buildroot] [PATCH 1/1] package/python-asyncssh: new package James Hilliard
2023-12-25 10:29 ` Thomas Petazzoni via buildroot [this message]
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=20231225112934.237a2b76@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.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