f93361979a
'install -d' has an issue compared to 'mkdir -p': it doesn't respect existing directories. It will set the ownership, file mode, and SELinux contexts (and any other property that would be set by install(1) to a newly-created directory), overwriting any existing properties of the existing directory. 'mkdir -p' doesn't have this issue: it is a no-op if the directory exists. However, it's not an ideal solution either, since it can't be used to set the properties (owner, mode, ...) of a newly-created directory. Therefore, the best solution is to use install(1), but only after making sure that the directory doesn't exist with test(1). Reported-by: Andrew Clayton <a.clayton@nginx.com> Reported-by: Alejandro Colomar <alx@nginx.com> Closes: <https://github.com/nginx/unit/issues/769> Signed-off-by: Alejandro Colomar <alx@nginx.com> Tested-by: Andrew Clayton <a.clayton@nginx.com> Reviewed-by: Andrew Clayton <a.clayton@nginx.com> |
||
---|---|---|
.. | ||
cc | ||
echo | ||
modules | ||
os | ||
atomic | ||
capability | ||
clang | ||
events | ||
feature | ||
files | ||
have | ||
help | ||
isolation | ||
make | ||
malloc | ||
mmap | ||
options | ||
pcre | ||
save | ||
sendfile | ||
shmem | ||
sockets | ||
sources | ||
ssltls | ||
summary | ||
test_build | ||
threads | ||
time | ||
types | ||
unix |