Annotate
makefile: fix prosody.version target
POSIX is quite explicit regarding the precedence of AND-OR lists [0]:
> The operators "&&" and "||" shall have equal precedence and shall be
> evaluated with left associativity. For example, both of the following
> commands write solely `bar` to standard output:
> false && echo foo || echo bar
> true || echo foo && echo bar
Given that, `prosody.version` target behaves as
((((((test -f prosody.release && cp ...) ||
test -f ...) &&
sed ...) ||
test -f ...) &&
hexdump ...) ||
echo unknown > $@)
In the case of release tarballs, `prosody.release` does exist, so the
first AND pair is executed. Given that it's successful, then the first
`test -f` in the OR pair is ignored, and instead the `sed` in the AND
pair is executed. `sed` success, as `.hg_archival.txt` exists, making
the second `test -f` in the OR pair ignored, and `hexdump` in the AND
pair is executed. Now, given that `.hg` doesn't exist, it fails, so the
last `echo` is run, overwriting `prosody.version` with `unknown`.
This can be worked around placing `()` around the AND pairs. Decided to use
conditionals instead, as I think they better communicate the intention
of the block.
[0]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_03
author |
Lucas <lucas@sexy.is> |
date |
Sun, 15 Aug 2021 04:10:36 +0000 |
parent |
5403:d7ecf6cd584e |
rev |
line source |
5403
|
1
|
|
2 The Prosody project is open to contributions (see HACKERS file), but is
|
|
3 maintained daily by:
|
94
|
4
|
5403
|
5 - Matthew Wild (mail: matthew [at] prosody.im)
|
|
6 - Waqas Hussain (mail: waqas [at] prosody.im)
|
|
7 - Kim Alvefur (mail: zash [at] prosody.im)
|
|
8
|
|
9 You can reach us collectively by email: developers [at] prosody.im
|
|
10 or in realtime in the Prosody chatroom: prosody@conference.prosody.im
|