Long term TODO: ensure cnf/config.guess and cnf/config.sub stay up-to-date

[fingolfin]

We currently have cnf/config.guess and cnf/config.sub as part of our repository. The reason is that while for projects using automake, the automake resp. autoreconf scripts install them -- but autoreconf does not do that when not using automake.

For now we have fairly recent versions in the repository, and I added a script cnf/update-config.sh to fetch the latest versions. But perhaps we should somehow automate this... or add a reminder that makes us run the script every couple months?

I guess what I am really asking here is: How can ensure that this and other things that need to be checked rarely but regularly can be taken care of?

In other projects, I'd do this by adding a step to the "release checklist", but we currently don't have one (but see issue #1477 -- if we implemented that, it would immediately allow to resolve this issue).

[fingolfin]

We could actually set up a GH Actions workflow which checks for new versions of these files once a month or so, and if found, open up a pull request. We already have workflows which open PRs in the GapWWW and PackageDistro repositories, which one can look at as a template.

[fingolfin]

Creating PRs can be done using https://github.com/peter-evans/create-pull-request