Summary: | Command Line Option for forcing color output missing | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Danny Milosavljevic <danny_milo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED LATER | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | adds a --nocolor option |
Description
Danny Milosavljevic
2003-03-02 13:25:12 UTC
'upgradeonly' has been filed before as a different bug I suppose you mean Bug #12069 or Bug #13632. But the wish for a make.conf option is missing there. The "upgradeonly" stuff in general _has_ been implemented in recent portage releases (-U). But no make.conf setting instead of -U exists :) hm, still no command line option for forcing color output... That would be good for: emerge search whatever |lv -c to be colory ;) it also is just a minor change... nobody wants to do it ? Created attachment 56720 [details, diff]
adds a --nocolor option
Probably a bad spot to add the nocolor call, but hey emerge is screwed up nuff
anyway :)
isnt your patch the wrong way around ? I dont have any problem getting portage NOT to use color. The moment you use a pipe, color is gone. The point is I WANT to have color and a pipe :) example, emerge search xyz |lv -c to have a colored, scrolling list of packages A new color={on,off,auto} could be introduced, but as talking with Jason on IRC about it has revealed, it will most likely be pushed back to whenever emerge gets gutted and rewritten. Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;) I think this is fixed by now. This is fixed in >=portage-2.1.2_rc1-r3. See bug #42115. |