Haiku/haiku
Haiku/haiku
1
0
Fork 0
mirror of https://review.haiku-os.org/haiku synced 2024-11-23 07:18:40 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

configure: Ensure the git checkout was not done with a restrictive umask.

Browse Source 
It seems that the old buildbots had their (ancient) checkouts done with a
restrictive umask, and this meant that some files in buildbot-generated
builds were not readable by "world" as they should have been.

Now instead of just verifying the umask itself is not too restrictive,
we also validate the "SetupEnvironment" script in the tree has mode 644.

Fixes #14085.
This commit is contained in:
Augustin Cavalier 2018-10-20 23:03:14 +00:00
parent 7852aa0525
commit 02f3646adc
1 changed files with 15 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
configure vendored
View File

@ -535,10 +535,23 @@ for var in `env`; do
done
# ensure umask is not too restrictive
if [ $(umask) -gt 22 ]; then
echo "Your umask is too restrictive (should be: <= 0022; is actually:" $(umask)")"
if [ `umask` -gt 22 ]; then
echo Your umask is too restrictive "(should be <= 0022;" is actually `umask`")"
echo
echo Additionally, if the source tree was cloned with a too-restrictive umask,
echo you will need to run \"git checkout\" again to fix this.
exit 1
fi
# ensure git checkout was not done with a restrictive umask
if [ `stat -c '%a' $sourceDir/data/system/boot/SetupEnvironment` -ne 644 ]; then
echo "The source tree was cloned with a umask > 0022. It seems you"
echo have already corrected your umask, but not re-checked-out the
echo source tree. Try running:
echo " git checkout --force"
echo to fix this problem.
exit 1
fi
# internal default parameter values
#