text files have wrong permissions in trunk
Bug #250924 reported by
Michael Rooney
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| wxBanker |
Fix Released
|
Medium
|
Michael Rooney | ||
Bug Description
README.txt and UPGRADING.txt are "-rw-r--r--", but every other file is "-rwxr-xr-x". I don't know if the execute bit makes sense for text files, but I think it is just as simple as a chmod a+x.
Note that the old README was "-rwxr-xr-x", so they should probably all be the same.
| Changed in wxbanker: | |
| assignee: | nobody → michael |
| importance: | Undecided → Medium |
| milestone: | none → 0.3 |
| status: | New → Confirmed |
| status: | Confirmed → Triaged |
Revision history for this message
| Michael Rooney (mrooney) wrote | #1 |
Revision history for this message
| Michael Rooney (mrooney) wrote | #2 |
| Changed in wxbanker: | |
| status: | Triaged → Fix Committed |
Revision history for this message
| Michael Rooney (mrooney) wrote | #3 |
| Changed in wxbanker: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Actually I think I'll solve this the other way, having only .py files as executable. That means README.txt and UPGRADING.txt are fine, and we need to chmod a-x gpl.txt, as well as the images in /art. I don't think executing text files makes sense.
The python files may not even need it -- almost no python AWN applets have it, but I think it is aids in allowing double-clicking, perhaps, or ./*.py, which makes perfect sense. So let's keep it for those.