Description
Feature or enhancement
Proposal:
Follow-up from #112090 and related to python/release-tools#70, I am proposing using the regen-configure makefile target in release tools and therefore need to add the target in each branch. There will be no changes to the version of autotools used, I'll continue using the existing quay.io image corresponding to each branch.
After all branches are updated, I'll create an update to release-tools to use make regen-configure instead of its own implementation of that process to avoid per-branch differences.
While I'm there I'll be pinning to a sha256 manifest instead of using a tag to prevent a update upstream from being able to inject into the release process. I don't forsee these images needing an update (they haven't been updated in over 2 years) but if that's an incorrect assumption let me know!
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
Talked with @pablogsal already for 3.10 and 3.11 branches. Need to confirm with @ambv for 3.9 and 3.8.
Linked PRs
- [3.11] GH-112160: Pin to manifest of quay.io/tiran/cpython_autoconf #112161
- [3.10] gh-112160: Add 'regen-configure' make target #112163
- [3.9] gh-112160: Add 'regen-configure' make target #112164
- [3.8] gh-112160: Add 'regen-configure' make target #112167
- [3.11] gh-112160: Backport 'Tools/build/regen-configure.sh' script #114333