Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Cc: "Michał Górny" <mgorny@g.o>, Zac Medico <zmedico@g.o>
Subject: [gentoo-portage-dev] [PATCH] estrip: Report pre-stripped files even with RESTRICT=strip
Date: Tue, 02 Oct 2018 19:01:39
Message-Id: 20181002190111.22154-1-zmedico@gentoo.org
1 From: Michał Górny <mgorny@g.o>
2
3 The purpose of RESTRICT=strip is to prevent files from being stripped,
4 not to silence QA checks about pre-stripped files.
5
6 Signed-off-by: Zac Medico <zmedico@g.o>
7 ---
8 bin/estrip | 2 +-
9 1 file changed, 1 insertion(+), 1 deletion(-)
10
11 diff --git a/bin/estrip b/bin/estrip
12 index 3ee4b01ac..369755cfe 100755
13 --- a/bin/estrip
14 +++ b/bin/estrip
15 @@ -308,7 +308,7 @@ process_elf() {
16 # The existance of the section .symtab tells us that a binary is stripped.
17 # We want to log already stripped binaries, as this may be a QA violation.
18 # They prevent us from getting the splitdebug data.
19 -if ! ${RESTRICT_binchecks} && ! ${RESTRICT_strip} ; then
20 +if ! ${RESTRICT_binchecks} ; then
21 # We need to do the non-stripped scan serially first before we turn around
22 # and start stripping the files ourselves. The log parsing can be done in
23 # parallel though.
24 --
25 2.16.4