Add a lint to check for source file permissions
Categories
(Developer Infrastructure :: Lint and Formatting, enhancement)
Tracking
(firefox70 fixed)
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: Sylvestre, Assigned: Sylvestre)
References
Details
Attachments
(3 external files)
Detect if the source file has +x permissions and set the right permissions.
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
Depends on D42672
Comment 6•7 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•7 years ago
|
Updated•7 years ago
|
| Assignee | ||
Comment 8•7 years ago
|
||
Depends on D42672
Comment 10•7 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/3076039dfbf4
https://hg.mozilla.org/mozilla-central/rev/cd3f609f0081
Comment 11•7 years ago
|
||
Is this meant to do something on Windows, which doesn't really have a real sense of +x ? Right now it seems to warn for all the files in m-c...
| Assignee | ||
Comment 12•7 years ago
|
||
Nope, where do you see that?
Comment 13•7 years ago
|
||
(In reply to Sylvestre Ledru [:Sylvestre] from comment #12)
Nope, where do you see that?
$ ./mach lint --outgoing
path/to/mozilla-central/browser/app/nsBrowserApp.cpp
0 error Execution permissions on a source file (file-perm)
path/to/mozilla-central/browser/app/winlauncher/LauncherProcessWin.cpp
0 error Execution permissions on a source file (file-perm)
0 error Execution permissions on a source file (file-perm)
path/to/mozilla-central/toolkit/xre/CmdLineAndEnvUtils.h
0 error Execution permissions on a source file (file-perm)
path/to/mozilla-central/toolkit/xre/nsAppRunner.cpp
0 error Execution permissions on a source file (file-perm)
? 5 problems (5 errors, 0 warnings)
I don't know why LauncherProcessWin shows up twice, and I haven't touched any permissions as part of writing a patch (patch is up on https://phabricator.services.mozilla.com/D44395 in case it's relevant)...
| Assignee | ||
Comment 14•7 years ago
|
||
ok, merci!
I guess we should just disable the check on Windows (which I did in the bug 1578673)
Updated•4 years ago
|
Description
•