On Sun, Aug 16, 2015 at 21:52:26 -, James Johnston wrote:
d. If the answer to (c) is yes, should that keyword become the default,
subject to a new policy? (And introduction of a different NO_RESPECT_UMASK
keyword).
FWIW, the install(1) tool does not respect umask by default (and has
On 08/16/2015 05:52 PM, James Johnston wrote:
a. So to clarify, you'd want existing OWNER_* / GROUP_* / EXECUTE_*
options to remain unmodified? i.e. if you install(PERMISSIONS GROUP_WRITE)
this will still NOT respect the umask, correct? (i.e. the only way to
respect the umask would be
Hi,
I figured I'd take a look at resolving #10126:
http://www.cmake.org/Bug/view.php?id=10126
The fix proposed by Brad King at this ticket involves two parts. I'd like
to seek clarification on this ticket.
1. It is proposed to add new file permissions to INSTALL and FILE commands
called
