aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/patches
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-05-06 00:45:22 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-05-06 01:15:29 +0100
commit22d915e020643797eab6f3f3017752cb1f6b0178 (patch)
tree346cb01855cf090ac27102c6ae227e91c0d14e5f /reproduce/software/patches
parent82666074e0c921e53c21b9e2c444e9a2d407d092 (diff)
Software are rebuilt automatically with change of version
Until now, when you changed the version of a software in an already-built system, its tarball would be downloaded, but it wouldn't actually build. The only way would be to force the build by deleting the main target of that file (under `.local/version-info/TYPE/PROGRAM'). This was because the tarballs were an order-only prerequisite which was implemented some time ago based on some theoretical argument that if the tarball dates changes, the software should not be rebuilt (because we check the checksum). However, the problems this causes are more than those it solves: Users may forget to delete the main target of the program and mistakenly think that they are using the new version. The fact that all the numbers going into the paper also contain this number further hides this. With this commit, tarballs are no longer order-only and any time a version of a software is updated, it will be automatically built and not cause confusion and manual intervention by the users. As a result of this change, I also had to correct the way we find the tarball from the list of prerequisites.
Diffstat (limited to 'reproduce/software/patches')
0 files changed, 0 insertions, 0 deletions