On Sat, May 27, 2017 at 3:05 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
Firstly, I don't see why the runtime loader would need execute permission.
It is not meant to be executed and AFAICT the permission isn't
checked/required anywhere.
Secondly, it isn't exactly a huge amount of work to have the package tool
adjust the permissions of added files and directories. It means adding a
switch to the tool ("create" and "add" commands), propagating the value to
the code responsible (i.e. add a flag [1] and use it), and modifying the
code that currently just copies the permission values to adjust them [2].
If no one cares to implement a proper solution, the issue can't be that
pressing. Given that a fairly simple work-around is to build with a less
restrictive umask, I don't see a good reason to add a hack-around. Those
temporary band-aid solutions tend to stay forever, so I'm generally wary of
introducing them.
