From: m4rcu5 <m4rcu5@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: esptool-3.1
Date: Thu, 22 Jul 2021 21:15:18 +0200 [thread overview]
Message-ID: <20210722191518.LkygR4TQBZIR09cKd4oe-fN3qe2LbQg6rWEAcunsFUQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31610@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
There is an updated pull request by m4rcu5 against master on the void-packages repository
https://github.com/m4rcu5/void-packages esptool
https://github.com/void-linux/void-packages/pull/31610
New package: esptool-3.1
#### General
- [X] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [X] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [X] I built this PR locally for my native architecture, (amd64)
No hardware hackers on Void? Or did I miss the boat on a way better tool to program ESP's?
`esptool` depends on `python3-reedsolo`, I've bundled both new packages in this PR.
I am doubting if I should strip the `.py` extension from the installed binaries, as the help output still references the binaries including the `.py` extension.
A patch file from https://github.com/void-linux/void-packages/pull/31610.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-esptool-31610.patch --]
[-- Type: text/x-diff, Size: 2259 bytes --]
From 71b8d55ed97072a923f725d04e237729e37158ab Mon Sep 17 00:00:00 2001
From: Marcus van Dam <marcus@marcusvandam.nl>
Date: Tue, 22 Jun 2021 11:43:22 +0200
Subject: [PATCH 1/2] New package: python3-reedsolo-1.5.4
---
srcpkgs/python3-reedsolo/template | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 srcpkgs/python3-reedsolo/template
diff --git a/srcpkgs/python3-reedsolo/template b/srcpkgs/python3-reedsolo/template
new file mode 100644
index 000000000000..654c6f40d8ce
--- /dev/null
+++ b/srcpkgs/python3-reedsolo/template
@@ -0,0 +1,18 @@
+# Template file for 'python3-reedsolo'
+pkgname=python3-reedsolo
+version=1.5.4
+revision=1
+wrksrc="reedsolomon-${version}"
+build_style=python3-module
+hostmakedepends="python3-setuptools python3-Cython"
+makedepends="python3-devel"
+short_desc="Pure-python Reed Solomon encoder/decoder"
+maintainer="Marcus van Dam <marcus@marcusvandam.nl>"
+license="MIT"
+homepage="https://github.com/tomerfiliba/reedsolomon"
+distfiles="${homepage}/archive/v${version}.tar.gz"
+checksum=cbe74633d1e3ff0f3b9c44fac06dff3355c622e93d4a0cd85116c909932af665
+
+post_install() {
+ vlicense LICENSE
+}
From 6ce89411d59bf6ea59f702e67bf49450fa046eaa Mon Sep 17 00:00:00 2001
From: Marcus van Dam <marcus@marcusvandam.nl>
Date: Tue, 22 Jun 2021 11:45:44 +0200
Subject: [PATCH 2/2] New package: esptool-3.1
---
srcpkgs/esptool/template | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 srcpkgs/esptool/template
diff --git a/srcpkgs/esptool/template b/srcpkgs/esptool/template
new file mode 100644
index 000000000000..fed492d617e5
--- /dev/null
+++ b/srcpkgs/esptool/template
@@ -0,0 +1,14 @@
+# Template file for 'esptool'
+pkgname=esptool
+version=3.1
+revision=1
+build_style=python3-module
+hostmakedepends="python3-setuptools python3-pip"
+depends="python3-pyserial python3-ecdsa python3-pyaes
+ python3-bitstring python3-reedsolo"
+short_desc="Utility to communicate with the ROM bootloader in ESP8266 & ESP32 chips"
+maintainer="Marcus van Dam <marcus@marcusvandam.nl>"
+license="GPL-2.0-or-later"
+homepage="https://github.com/espressif/esptool"
+distfiles="${homepage}/archive/v${version}.tar.gz"
+checksum=5edc768a63df4d73bdeba534146f6b3e41fbbe3c25f08be627733fc38535a976
next prev parent reply other threads:[~2021-07-22 19:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 10:10 [PR PATCH] " m4rcu5
2021-07-20 7:14 ` m4rcu5
2021-07-20 12:29 ` [PR REVIEW] " ericonr
2021-07-20 12:29 ` ericonr
2021-07-20 12:29 ` ericonr
2021-07-22 19:12 ` [PR PATCH] [Updated] " m4rcu5
2021-07-22 19:12 ` [PR REVIEW] " m4rcu5
2021-07-22 19:14 ` m4rcu5
2021-07-22 19:15 ` m4rcu5 [this message]
2021-07-22 19:18 ` m4rcu5
2021-08-03 2:54 ` ericonr
2022-05-23 2:12 ` github-actions
2022-06-06 2:14 ` [PR PATCH] [Closed]: " github-actions
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=20210722191518.LkygR4TQBZIR09cKd4oe-fN3qe2LbQg6rWEAcunsFUQ@z \
--to=m4rcu5@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).