Arnout Engelen 078c2a7341 bash 5.1: don't rely on patch timestamps in build ... When, after patching, `configure.ac` is newer than `configure`, the Makefile will try to regenerate `configure` from `configure.ac`. While that might usually be desirable, in this case we want to keep bootstrapping simple and directly use the `configure` from the package so we can avoid a dependency on automake. Previously, we used the `-T` parameter to automake to make sure the timestamps were okay. However, this is brittle when we update: when the timestamp of the original file changes, and no longer matches the timestamp of the original file in the patch, `patch` will show a warning but otherwise continue without updating the timestamp. This PR changes things so we only patch `configure`, so that will always have a newer timestamp. We will update bash-4.4 in a separate PR (but that one has a bigger rebuild impact so will have to target staging) Refs #115177		2021-03-22 12:27:10 +01:00
..
bash-completion
nix-bash-completions
4.4.nix
5.1.nix	bash 5.1: don't rely on patch timestamps in build	2021-03-22 12:27:10 +01:00
bash-4.4-patches.nix
bash-5.1-patches.nix
cygwin-bash-4.4.11-2.src.patch
pgrp-pipe-4.4.patch
pgrp-pipe-5.1.patch	bash 5.1: don't rely on patch timestamps in build	2021-03-22 12:27:10 +01:00
update-patch-set.sh