aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/make/atlas-multiple.mk
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-12-14 02:14:34 +0000
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-12-14 02:28:14 +0000
commitb910b2e493972db368874752ac033ab7c41696dd (patch)
treeb3cd02b575a348d8848f60a1438630abcea3a0cb /reproduce/software/make/atlas-multiple.mk
parentcce4016a516fcac50a71b78a0d0e66caed75ce5f (diff)
Better warnings when maneage branch not present and PDF not built
Until now, there was no warning when the 'maneage' branch didn't exist in the Git history. This can happen when you forget to push the 'maneage' branch to a remote for your project, and you later clone your project from that remote (for example on another computer). We use the 'maneage' branch to report the latest commit hash and date in the final paper (which can greatly help future readers). Since we check the 'maneage' branch on every run of './project make' (in 'initialize.mk') this would result in a printed statement like this: fatal: Not a valid object name maneage Also until now, the description of what to do when TeXLive wasn't installed properly wasn't complete: it didn't mention that it is necessary to delete the TeXLive target files. This could confuse users (they would re-run './project configure -e', but with no effect). With this commit, for the 'maneage' branch issue a complete warning will be printed. Telling the user what to do to get the 'maneage' branch (and thus fix this warning). Also, the LaTeX macros that go in the paper are now red when the 'maneage' branch doesn't exist, telling the user to see the printed warning (thus encouraging the user to get the branch). For the TeXLive issue, the necessary commands to run are now also printed in the warning.
Diffstat (limited to 'reproduce/software/make/atlas-multiple.mk')
0 files changed, 0 insertions, 0 deletions