diff options
| author | Arnout Engelen <arnout@bzzt.net> | 2021-03-22 12:27:10 +0100 |
|---|---|---|
| committer | Arnout Engelen <arnout@bzzt.net> | 2021-03-22 12:27:10 +0100 |
| commit | 078c2a734110b80195781442b2c227b3027a734f (patch) | |
| tree | bfb420618e6fe21787c32b6833bf8e4af7a57dd3 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | f5e8bdd07d1afaabf6b37afc5497b1e498b8046f (diff) | |
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
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions