Summary: | another /dev/stdout permission fix | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Max Kalika (RETIRED) <max> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | blkdeath |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | ebuild.sh-2.0.49-stdout_permission_fix.patch |
Description
Max Kalika (RETIRED)
![]() Created attachment 16607 [details, diff]
ebuild.sh-2.0.49-stdout_permission_fix.patch
Why not simply look in /proc/self/fd instead of /dev/fd? This way systems without a running devfsd would also work fine. Agreed. I'd like to see this fixed in portage as well. in my local ebuild.sh I simply do [ -w /dev/stdout ] && tty --quiet < /dev/stdout || echo "${x}" works like a charm. Modified and included. Per-Ebuild logging breaks this benefit, I just realized... but it helps to keep depend info clean, which is good. |