Install is writing in my build directory
hmurray at megapathdsl.net
Fri Dec 29 11:16:13 UTC 2017
Is that expected? Why? ...
waf check does it too. So does a redundant waf build.
I'd like a way to test that everything is ready to install. I'd expect waf
check to do that.
[ 97/104] Processing /home/murray/ntpsec/raw/build/main/pylib/control.py:
wafhelpers/pythonize-header include/ntp_control.h ->
[ 98/104] Processing /home/murray/ntpsec/raw/build/main/pylib/magic.py:
wafhelpers/pythonize-header include/ntp.h -> build/main/pylib/magic.py
[ 99/104] Processing /home/murray/ntpsec/raw/build/main/pylib/version.py,/home
wafhelpers/autorevision.sh -> build/main/pylib/version.py
Here is why I noticed it? (after a sudo install)
[murray at hgm raw]$ ls -l build/main/pylib/ | grep root
-rw-r--r-- 1 root root 4648 Dec 29 03:02 control.py
-rw-r--r-- 1 root root 4557 Dec 29 03:02 magic.py
-rw-r--r-- 1 root root 484 Dec 29 03:02 version.py
[murray at hgm raw]$
While poking around, I also saw one case where the link ntp -> pylib was also
owned by root.
Context is I did a sudo around the script I use to install with DESTDIR=foo
to test some code that sets up ntpd to setuid as user ntp, then discovered a
simple rm -r on my build directory asked me about those files?
These are my opinions. I hate spam.
More information about the devel