Hi Holger
Thanks for working on this :)
- The list of archs is hardcoded in the Makefile for now.
The following might provide you with some useful way of not hard-coding
such information:
curl -s 'https://api.ftp-master.debian.org/suite/bookworm'
(pipe that into « jq -r '.architectures[]' » to get just the archs as
plain text)
You might want to make that a 'maintainer-run' step rather than is run
occasionally as part of preparing a release, rather than as a build time
step. That is, the maintainer runs that from a machine with internet
access to find the list of archs that should be used; this is then
cached in the repo until it is next refreshed. There is precedent for
this 'maintainer-run' step in various "make dist' mechanisms (from the
autotools world) and how the dh-python packages prepares a cache of
known python modules in the archive for later module→package translation.
There has been talk for a while about how we might avoid baking in
internal metadata in packages and there might be more inspiration on how
to do this in other parts of the project:
https://wiki.debian.org/SuitesAndReposExtension
(there are already a couple of entries there for the release notes)
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
