Package Details: python-amulet-compiler-target 2.0-1

Git Clone URL: https://aur.archlinux.org/python-amulet-compiler-target.git (read-only, click to copy)
Package Base: python-amulet-compiler-target
Description: A token library to pin compile-time requirements
Upstream URL: https://github.com/Amulet-Team/Amulet-Compiler-Target
Licenses: LicenseRef-Amulet-Team-License
Submitter: Kimiblock
Maintainer: Kimiblock (lilac)
Last Packager: lilac
Votes: 1
Popularity: 0.147543
First Submitted: 2025-06-21 15:12 (UTC)
Last Updated: 2025-06-24 12:18 (UTC)

Latest Comments

gwuensch commented on 2025-08-20 01:33 (UTC) (edited on 2025-08-20 01:39 (UTC) by gwuensch)

In a clean chroot build, files created during compilation shouldn't persist across builds.

That's correct, but you can't expect everyone to always build in a clean chroot. It is common practice to make sure source files are unique or conflicting files get cleaned up. This is mentioned in many wiki articles, such as the one I linked.

Unique source directory will have to completely re-download source git repo every update, which is not desired since makepkg does not support specifying depth.

I see this point, but isn't this also true when always building in a clean chroot? The alternative would be including git clean -fdx, which I'm also fine with.

Edit: Specifically, python -m installer only expects one file, while dist/*.whl will also pick up outdated wheels from previous builds. There might be other issues not so apparent. The wiki generally advises to remove "stale wheels along with other build artifacts".

Kimiblock commented on 2025-06-26 14:34 (UTC)

@gwuensch Could you be more specific that why stale wheels will lead to errors? In a clean chroot build, files created during compilation shouldn't persist across builds. Unique source directory will have to completely re-download source git repo every update, which is not desired since makepkg does not support specifying depth.

gwuensch commented on 2025-06-26 12:39 (UTC) (edited on 2025-06-26 12:42 (UTC) by gwuensch)

At the moment, stale wheels will lead to errors when packaging. Could you update the source dir to be unique for each version? For example, "${pkgname#python-}-${pkgver}::git+...

Or, alternatively, include a git clean -fdx in prepare(). But I think a directory for each version is nicer as this is not a VCS package.