[gentoo-portage-dev] [PATCH] portage.output: Replace darkblue colors with teal

2021-12-03 Thread Michał Górny
The "darkblue" color is often barely visible on dark terminals which
makes reading emerge output really hard (I basically have to copy-paste
it a lot in order to be able to read it at all).  Replace it with teal
that does not seem to have any significant use in the output.

Signed-off-by: Michał Górny 
---
 lib/portage/output.py | 6 +++---
 man/color.map.5   | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)


The before-after screenshot can be found on the PR:
https://github.com/gentoo/portage/pull/776


diff --git a/lib/portage/output.py b/lib/portage/output.py
index 42f487f8a..77375b012 100644
--- a/lib/portage/output.py
+++ b/lib/portage/output.py
@@ -157,7 +157,7 @@ _styles["UNMERGE_WARN"] = ("red",)
 _styles["SECURITY_WARN"] = ("red",)
 _styles["MERGE_LIST_PROGRESS"] = ("yellow",)
 _styles["PKG_BLOCKER"] = ("red",)
-_styles["PKG_BLOCKER_SATISFIED"] = ("darkblue",)
+_styles["PKG_BLOCKER_SATISFIED"] = ("teal",)
 _styles["PKG_MERGE"] = ("darkgreen",)
 _styles["PKG_MERGE_SYSTEM"] = ("darkgreen",)
 _styles["PKG_MERGE_WORLD"] = ("green",)
@@ -165,8 +165,8 @@ _styles["PKG_BINARY_MERGE"] = ("purple",)
 _styles["PKG_BINARY_MERGE_SYSTEM"] = ("purple",)
 _styles["PKG_BINARY_MERGE_WORLD"] = ("fuchsia",)
 _styles["PKG_UNINSTALL"] = ("red",)
-_styles["PKG_NOMERGE"] = ("darkblue",)
-_styles["PKG_NOMERGE_SYSTEM"] = ("darkblue",)
+_styles["PKG_NOMERGE"] = ("teal",)
+_styles["PKG_NOMERGE_SYSTEM"] = ("teal",)
 _styles["PKG_NOMERGE_WORLD"] = ("blue",)
 _styles["PROMPT_CHOICE_DEFAULT"] = ("green",)
 _styles["PROMPT_CHOICE_OTHER"] = ("red",)
diff --git a/man/color.map.5 b/man/color.map.5
index 288bf7fbd..92a1baa91 100644
--- a/man/color.map.5
+++ b/man/color.map.5
@@ -40,7 +40,7 @@ Defines color used for numbers indicating merge progress.
 \fBPKG_BLOCKER\fR = \fI"red"\fR
 Defines color used for unsatisfied blockers.
 .TP
-\fBPKG_BLOCKER_SATISFIED\fR = \fI"darkblue"\fR
+\fBPKG_BLOCKER_SATISFIED\fR = \fI"teal"\fR
 Defines color used for satisfied blockers.
 .TP
 \fBPKG_MERGE\fR = \fI"darkgreen"\fR
@@ -63,10 +63,10 @@ package.
 Defines color used for world packages planned to be merged using a binary
 package.
 .TP
-\fBPKG_NOMERGE\fR = \fI"darkblue"\fR
+\fBPKG_NOMERGE\fR = \fI"teal"\fR
 Defines color used for packages not planned to be merged.
 .TP
-\fBPKG_NOMERGE_SYSTEM\fR = \fI"darkblue"\fR
+\fBPKG_NOMERGE_SYSTEM\fR = \fI"teal"\fR
 Defines color used for system packages not planned to be merged.
 .TP
 \fBPKG_NOMERGE_WORLD\fR = \fI"blue"\fR
-- 
2.34.1




[gentoo-dev] Last rites: net-analyzer/amap

2021-12-03 Thread Jonas Stein

# Jonas Stein  (2021-12-01)
# Removal on 2022-01-01.
# Disbanded by upstream who suggested to
# use nmap instead many years ago. (bug #680546)
net-analyzer/amap



Re: [gentoo-dev] Common options missed in OpenRC declarative scripts and how to improve them

2021-12-03 Thread Marc Schiffbauer
* Michael Orlitzky schrieb am 02.12.21 um 08:05 Uhr:
> On 2021-12-02 08:12:55, Alec Warner wrote:
> > 
> > Can we automate any of it? Emit QA warnings? etc.
> > 
> 
> I would love to be proven wrong, but I don't think so. We have two
> main problems. First, The service scripts are POSIX sh, which is
> better than bash, but still can't easily be parsed for semantic
> information.
> 
> Second, if the daemon is "special," then the service script is
> justified in being similarly unconventional. Unusual runtime behavior
> can't be statically detected, and I doubt that the well-behaved
> portion of daemons in the tree is large enough that we can warn about
> every script that smells a little bit fishy.

For "special" daemons, the ebuild could just set a QA_* variable to 
silence a qa warning if required.

-Marc