Hey everyone,

Thanks for the discussion and taking interest in improving the
situation. After re-reading the thread, I propose the following plan. I
propose myself to implement it as well.

* The plan

** Part 1: implementation

substitute* stays the same, but gets deprecated in favor of:

`substitute-file`
        Substitutes one or multiple files, all regexes must
        match for all files. Takes optional argument to make each regex only
        have to match once.

There is no option to have a regex that never matches.

Documentation is updated. News entry is made.

** Part 2: migration

Every substitute* with only one file as argument gets replaced with
substitute-file. One CI rebuild round. Important packages are fixed,
others keep using deprecated substitute*.

Then we start again with all the other substitute*.


Part 2 is significantly harder than part 1 in my opinion, however part 1
is already a significantly better situation and ensures that any new
code is written using a robust substitute.

I’ll start working on part 1 tomorrow, if there are no objections.

Good day,
Noé

Attachment: signature.asc
Description: PGP signature

              • ... Jason Conroy
              • ... Development of GNU Guix and the GNU System distribution.
              • ... Jason Conroy
              • ... Development of GNU Guix and the GNU System distribution.
              • ... Andreas Enge
              • ... Jason Conroy
              • ... Andreas Enge
              • ... Andreas Enge
              • ... Jason Conroy
          • ... Ludovic Courtès
  • Re: Criticism of ... Development of GNU Guix and the GNU System distribution.

Reply via email to