Summary: | emerge could print all lines with 'world' packages in bold (or colour) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | list-ener |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 181949 | ||
Attachments: | portage-2.1.3_rc5 patch to make colors customizable via color.map |
Description
list-ener
2006-08-01 15:27:49 UTC
Interesting idea. I like it, but I think it's better if we isolate the worldfile handling first. Created attachment 123035 [details, diff]
portage-2.1.3_rc5 patch to make colors customizable via color.map
With this patch there are 4 new color classes that you can customize via /etc/portage/color.map:
PKG_MERGE=darkgreen
PKG_MERGE_WORLD=green
PKG_NOMERGE=darkblue
PKG_NOMERGE_WORLD=blue
This has been released in 2.1.3_rc6. It now supports a total of 7 color classes for /etc/portage/color.map: # packages given as command line arguments PKG_MERGE_ARG=darkgreen PKG_NOMERGE_ARG=darkblue # packages in /var/lib/portage/world PKG_MERGE_WORLD=green PKG_NOMERGE_WORLD=blue # system packages PKG_MERGE_SYSTEM=green PKG_NOMERGE_SYSTEM=blue # packages in --tree display that aren't being # merged and aren't part of any set PKG_NOMERGE=darkblue |