From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/python-snmpclitools: new package
Date: Tue, 8 Oct 2019 22:57:04 +0200 [thread overview]
Message-ID: <20191008225704.2547dffe@windsurf> (raw)
In-Reply-To: <20191008072801.3745-3-asafka7@gmail.com>
On Tue, 8 Oct 2019 10:28:01 +0300
Asaf Kahlon <asafka7@gmail.com> wrote:
> For now, we use PKG-INFO as license file, since LICENSE.rst isn't
> provided with the tarball.
> A pull request was sent upstream:
> https://github.com/etingof/snmpclitools/pull/11
>
> Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
I am wondering if this package shouldn't be named just "snmpclitools",
like upstream. In fact, contrary to the Python modules named
python-<something>, here the fact that it is Python is just an
implementation detail. Look at package/circus or package/crudini for
example.
And then of course, instead of being in the Python modules section, it
should be in the Networking tools section. And have a proper depends on
BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3 (depending on which one is
applicable, or both).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-08 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 7:27 [Buildroot] [PATCH 1/2] package/python-pysnmp-apps: remove package Asaf Kahlon
2019-10-08 7:28 ` [Buildroot] [PATCH 1/1] package/python-pytz: bump to version 2019.3 Asaf Kahlon
2019-10-08 21:07 ` Thomas Petazzoni
2019-10-08 7:28 ` [Buildroot] [PATCH 2/2] package/python-snmpclitools: new package Asaf Kahlon
2019-10-08 20:57 ` Thomas Petazzoni [this message]
2019-10-08 20:54 ` [Buildroot] [PATCH 1/2] package/python-pysnmp-apps: remove package 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=20191008225704.2547dffe@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox