Hello, here is the patch for updating to v5.5 (save it as update-to-5.5.patch and run git apply update-to-5.5.patch):
diff --git a/PKGBUILD b/PKGBUILD
index 05250c0..fff8abd 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,18 +1,18 @@
# Maintainer: Alex Henrie <alexhenrie24@gmail.com>
pkgname=esp-idf
-pkgver=5.4.1
-pkgrel=2
+pkgver=5.5
+pkgrel=1
pkgdesc="Espressif IoT Development Framework. Official development framework for ESP32."
arch=('i686' 'x86_64' 'aarch' 'aarch64' 'armv7h')
url="https://github.com/espressif/esp-idf"
license=('Apache-2.0')
-depends=('ccache' 'cmake' 'dfu-util' 'git' 'gperf' 'libusb' 'ninja' 'python')
+depends=('ccache' 'cmake' 'dfu-util' 'git' 'gperf' 'libusb' 'ninja' 'python' 'python-pip')
makedepends=('unzip')
options=('!strip')
install='esp-idf.install'
source=(https://github.com/espressif/${pkgname}/releases/download/v${pkgver}/${pkgname}-v${pkgver}.zip)
noextract=(${pkgname}-v${pkgver}.zip)
-sha256sums=('d78e49aafe46e35d34bc8804b64f23cd0a6cabdfe221876ba59f68b4534f0839')
+sha256sums=('54880b2565de01dc1d1210330e4514e8b2f816ea62219068ad943e6a0e8b588f')
prepare() {
unzip -o ${pkgname}-v${pkgver}.zip
--
2.49.0
I've sent this fix to the maintainer.
@TheAceBlock I see, thank you.
Does anyone know what was changed in release archive? Such changes look suspicious for me after the incident with xz.
Looks like the release zip file for the 5.4.1 release was recently updated, and the checksum changed.
It's now d78e49aafe46e35d34bc8804b64f23cd0a6cabdfe221876ba59f68b4534f0839.
In addition, the folder extracted from the zip now has the version in the path, requiring a small change to both cd ... lines.
Here's my patch to get it working:
diff --git a/PKGBUILD b/PKGBUILD
index 87e139c..9bc52e2 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -12,19 +12,19 @@ options=('!strip')
install='esp-idf.install'
source=(https://github.com/espressif/${pkgname}/releases/download/v${pkgver}/${pkgname}-v${pkgver}.zip)
noextract=(${pkgname}-v${pkgver}.zip)
-sha256sums=('6b6b9e7b5e1d6b946e6cfd062a3ce1cc8bb5957befdda683c2a0d9cb16a45015')
+sha256sums=('d78e49aafe46e35d34bc8804b64f23cd0a6cabdfe221876ba59f68b4534f0839')
prepare() {
unzip -o ${pkgname}-v${pkgver}.zip
}
build() {
- cd "$srcdir/${pkgname}"
+ cd "$srcdir/${pkgname}-v${pkgver}"
git submodule update --init
}
package() {
- cd "${srcdir}/${pkgname}"
+ cd "$srcdir/${pkgname}-v${pkgver}"
mkdir -p ${pkgdir}/opt/esp-idf
cp -R . ${pkgdir}/opt/esp-idf
}
I'm getting an error running the install script:
ERROR: tool openocd-esp32 is found in PATH, but has failed: non-zero exit code (127) with message: openocd: error while loading shared libraries: libcapstone.so.4: cannot open shared object file: No such file or directory
The script exits fine afterwards.
Looks like there's a dependency on capstone=4?
Hum, now I'm seeing a lot of
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
when building projects, so maybe we can't get away with dropping the .git directory.
... ah, but that won't work because it does a git submodule update in the build step.
We need to remove the .git directories after that. This can be done with
find . -path \*/.git/\* -delete -o -name .git -delete
That will remove the .git directory from the submodules, too.
So, this:
build() {
cd "$srcdir/${pkgname}-v${pkgver}"
git submodule update --init
find . -path \*/.git/\* -delete -o -name .git -delete
}
Which gives us a ~80MiB package, at around 450MiB when installed.
FWIW, you can skip extracting the .git directory altogether by adding the following at the end of the unzip command the prepare function:
... -x \*/.git/\*
So:
prepare() {
unzip -o ${pkgname}-v${pkgver}.zip -x \*/.git/\*
}
Am I talking to myself or what
