On Sun, 2020-11-15 at 16:40 +0100, Johannes Schauer wrote: > yes, it is pointless to attempt making the coverage.sh and make_mirror.sh > (those are the test suite) work across multiple releases such that I would > *not* have to make changes later. > ...
I see, makes sense. > The reason is, that I want to minimize the required dependencies of mmdebstrap > as much as possible, because mmdebstrap is supposed to run inside very minimal > environments. I wasn't aware of this design constraint, thanks for the info. The problem with the current setup is that it is hardcoding and in my experience, the hardcoding is forgotten about and doesn't get updated or it generates work for users, QA or other folks to detect the hardcoding and get it updated. Some alternatives to hardcoding in git to mitigate this: Hardcode at build time; build-depend on distro-info bits, extract the needed info and stash them in a (Perl?) file in the .deb package. After updates of distro-info in stable/oldstable, mmdebstrap can be binNMUed. Hardcode at release time; add a check to your release scripts to ensure that the hardcoded suite information is up-to-date with the latest version of distro-info available. Hardcode in a separate file; move the list of suite names that use the -security suffix instead of /updates out of the guts of the code into a separate file with a defined format, perhaps with a config file in /etc so the user can override it when it is outdated. The separate file should be more easily noticed than in the guts of the code. This option is best combined with the release-time checks. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
