aboutsummaryrefslogtreecommitdiff
path: root/test cases
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2021-11-18 17:52:12 -0500
committerEli Schwartz <eschwartz@archlinux.org>2022-08-23 21:07:00 -0400
commitf8ebfdf7b1f33f88007d107791a661a17827be43 (patch)
treee577c3ebc1ed54d2ce75c345c761e28665b4de6b /test cases
parentb7245d3f273dd6ddadc1fe2c2d06dbe25c1b9b5f (diff)
downloadmeson-f8ebfdf7b1f33f88007d107791a661a17827be43.zip
meson-f8ebfdf7b1f33f88007d107791a661a17827be43.tar.gz
meson-f8ebfdf7b1f33f88007d107791a661a17827be43.tar.bz2
install modes should not apply sticky bit to files
This is generally a bad idea, e.g. it causes OSError on freebsd. It also gets ignored by solaris and thus causes unittest failures. The proper solution is to simply reject any attempt to set this, and log a warning. The install_emptydir function does apply the mode as well, and since it is a directory it actually does something. This is the only place where we don't reset the mode. Although install_subdir also installs directories, and in theory it could set the mode as well, that would be a new feature. Also it doesn't provide much granularity and has mixed semantics with files. Better to let people use install_emptydir + install_subdir. Fixes #5902
Diffstat (limited to 'test cases')
-rw-r--r--test cases/common/190 install_mode/test.json9
1 files changed, 8 insertions, 1 deletions
diff --git a/test cases/common/190 install_mode/test.json b/test cases/common/190 install_mode/test.json
index 3614dbc..a58caa1 100644
--- a/test cases/common/190 install_mode/test.json
+++ b/test cases/common/190 install_mode/test.json
@@ -11,5 +11,12 @@
{"type": "file", "file": "usr/share/sub2/stub"},
{"type": "file", "file": "usr/subdir/data.dat"}
],
- "do_not_set_opts": ["libdir"]
+ "do_not_set_opts": ["libdir"],
+ "stdout": [
+ {
+ "line": ".* DEPRECATION: install_mode with the sticky bit on a file",
+ "match": "re",
+ "count": 3
+ }
+ ]
}