Waf build bug/quirk
hmurray at megapathdsl.net
Sun Feb 18 06:04:55 UTC 2018
If I run waf build after a clean build, It does this:
'build' finished successfully (0.451s)
--- building host ---
Waf: Entering directory `/home/murray/ntpsec/play/hgm/host'
Waf: Leaving directory `/home/murray/ntpsec/play/hgm/host'
--- building main ---
Waf: Entering directory `/home/murray/ntpsec/play/hgm/main'
[113/115] Processing /home/murray/ntpsec/play/hgm/main/pylib/control.py: wafhelpers/pythonize-header include/ntp_control.h -> hgm/main/pylib/control.py
[114/115] Processing /home/murray/ntpsec/play/hgm/main/pylib/magic.py: wafhelpers/pythonize-header include/ntp.h -> hgm/main/pylib/magic.py
[115/115] Processing /home/murray/ntpsec/play/hgm/main/pylib/version.py,/home/murray/ntpsec/play/wafhelpers/.autorevision-cache: VERSION wafhelpers/autorevision.sh -> hgm/main/pylib/version.py wafhelpers/.autorevision-cache
Waf: Leaving directory `/home/murray/ntpsec/play/hgm/main'
'build' finished successfully (0.456s)
What's going on?
waf install does a build, so if you run waf install as root, it leaves files behind that are owned by root. That's not polite.
These are my opinions. I hate spam.
More information about the devel