| Summary: | Ease build.log permissions | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Mira Ressel <aranea> |
| Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Mira Ressel
2016-11-04 14:33:59 UTC
Maybe we can just re-use PORTAGE_WORKDIR_MODE, and mask out the executable bits. (In reply to Zac Medico from comment #1) > Maybe we can just re-use PORTAGE_WORKDIR_MODE, and mask out the executable > bits. I like this proposal, but there's a catch: Per default, PORTAGE_WORKDIR_MODE is 0700, whereas build.log's permissions are 0660. If your idea is implemented, the default permissions of build.log would change to 0600. This might break some current workflows relying on build.log being readable by the portage group. I can think of two possibilities to avoid this: a) Change PORTAGE_WORKDIR_MODE's default to 0770 (or 0750?), and set build.log's permissions to PORTAGE_WORKDIR_MODE w/o the execute bits. b) Set build.log permissions to PORTAGE_WORKDIR_MODE w/o the execute bits, unless PORTAGE_WORKDIR_MODE hasn't been set by the user; in the latter case, set build.log's perms to 0660. PS: The permission bits in my previous comment are of course wrong and should be 0660 / 0664 instead. Ping? |
