Arch Linux User Repository

Added

can you add duktape to keywords?

Added.

Please provide a build for aarch64 again. The build works flawlessly.

Point 1: There is package_python-dukpy which is remnant of when this split package. If the tool you are using to build packages in clean chroot does not support this, then it is issue of the tool and not of the package. I always build using makechrootpkg and it works.

Point 2: No, it is not "definitely wrong" In your first comment you mentioned ${pkgdir} and not you mentioned ${srcdir}. I think I get what you mean now

In the past it was not the case, but as of "few years"(I don't know exactly when) the functions (with exeption of verify()) already "start" in $srcdir. You can check this with this minimal example:

pkgname=qwertyuiop
pkgver=1
pkgrel=1
arch=('any')

prepare() {
pwd
cd $srcdir
pwd
}
verify() {
pwd
cd $srcdir
pwd
}
build() {
pwd
cd $srcdir
pwd
}
check() {
pwd
cd $srcdir
pwd
}
package() {
pwd
cd $srcdir
pwd
}

It still does not build in a clean chroot for me. It is missing a package function and 'cd dukpy-${pkgver}' is definitely wrong and likely should be 'cd "${srcdir}/dukpy-${pkgver}"'

Have you seen https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

Fixed. I don't understand what you mean by "line 23 at a minimum needs to be referenced to ${pkgdir}".

This does not build in a clean chroot for me. I am pretty sure that the pkgname variable needs to be set (probably just uncomment line 4) and line 23 at a minimum needs to be referenced to ${pkgdir}

This is not proper way to do this. pip is definitely not needed to build, this issue was due to missing python-mutf8 checkdependency. Now that you have deleted check, this issue is no longer present.