[Omake] FS case-sensitivity testing - if the name is non-alpha,
should we still test.
Aleksey Nogin
anogin at hrl.com
Mon Jun 4 09:37:01 PDT 2007
Suppose somebody's path contains elements like:
/usr/x86_64-pc-linux-gnu/gcc-bin/4.2.0
/usr/kde/3.5/sbin
/usr/kde/3.5/bin
/usr/qt/3/bin
where the directories /usr/x86_64-pc-linux-gnu/gcc-bin, /usr/kde and
/use/qt _only_ contain numerical elements (this is a real example from,
I believe, Gentoo). As the PATH elements are converted to dir values,
OMake will try to create a tmp file in each of the 3 "numerical only"
directories (and fail, as it does not have write access).
Note that OMake does not really care about the case-sensitivity of those
directories - the item being creates is itself numerical, so it's
case-invariant anyway.
So the question is - should OMake be changed to only resort to
"invasive" testing (via the tmp file creation) when it actually cares?
The issue here is that the "audit" of access failures is becoming more
common (SELinux, etc, etc), so these tests are not always 100% harmless
(as they cause people to start wondering what is going on)...
Aleksey
More information about the OMake-Devel
mailing list