From: Ricardo Martincoski <ricardo.martincoski@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/8] package/asterisk: add comment about a check-package false positive
Date: Thu, 30 Nov 2017 09:19:41 -0200 (BRST) [thread overview]
Message-ID: <1054252197.2705387.1512040781069.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20171130090057.2d034d10@windsurf.home>
Hello,
On Thursday, November 30, 2017 6:00:57 AM, Thomas Petazzoni wrote:
> On Thu, 30 Nov 2017 00:08:44 +0100, Yann E. MORIN wrote:
[snip]
>> +++ b/package/asterisk/asterisk.mk
>> @@ -285,6 +285,7 @@ HOST_ASTERISK_LICENSE_FILES = COPYING
>>
>> # No need to autoreconf for the host variant,
>> # so do not inherit the target setup.
>> +# check-package reports an issue here, but that's a false positive. Ignore.
>> HOST_ASTERISK_AUTORECONF = NO
>
> I'm not sure we should have a comment here. Instead we should fix
> check-package: it is not normal for check-package to emit a warning
> here, since it is legal (currently) for a package to autoreconf its
> target variant, and not autoreconf its host variant.
I agree, it's better to not issue a false warning.
>
> Ricardo, do you think you could fix this problem in check-package ?
We can use something like this (not fully tested yet!):
+++ utils/checkpackagelib/lib_mk.py
@@ -219 +219 @@ class UselessFlag(_CheckFunction):
- if self.DEFAULT_AUTOTOOLS_FLAG.search(text):
+ if self.DEFAULT_AUTOTOOLS_FLAG.search(text) and not text.lstrip().startswith("HOST_"):
Avoiding false warnings is more important than testing for all corner
cases IMO. Using the code above we don't issue a valid warning for
rare cases, we stop issuing a false warning and we also keep O(n).
I will send it separately (after proper commit message and testing)
if Yann doesn't include something similar (feel free to do so!) to
the series before.
Regards,
--
Ricardo Martincoski
DATACOM
Ethernet Switches
Rua Am?rica, 1000 - Eldorado do Sul, RS - 92990-000 - Brasil
+55 51 3933 3000 - Ramal 3307
ricardo.martincoski at datacom.ind.br
www.datacom.ind.br
next prev parent reply other threads:[~2017-11-30 11:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 23:08 [Buildroot] [PATCH 0/8] Fix warnings reported by check-package Yann E. MORIN
2017-11-29 23:08 ` [Buildroot] [PATCH 1/8] package/lttng-tools: fix typo in variable name Yann E. MORIN
2017-11-30 7:58 ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 2/8] package/checkpolicy: rename variable Yann E. MORIN
2017-12-01 21:55 ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 3/8] package/am335x-pru-package: " Yann E. MORIN
2017-12-01 21:56 ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 4/8] package/lockfile-progs: " Yann E. MORIN
2017-12-01 21:56 ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 5/8] packages: remove "consecutive empty lines" Yann E. MORIN
2017-12-01 21:56 ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 6/8] packages: fix trailing spaces and slash Yann E. MORIN
2017-12-01 21:57 ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 7/8] package/asterisk: add comment about a check-package false positive Yann E. MORIN
2017-11-30 8:00 ` Thomas Petazzoni
2017-11-30 11:19 ` Ricardo Martincoski [this message]
2017-11-30 12:57 ` Thomas Petazzoni
2017-12-01 22:00 ` Thomas Petazzoni
2017-12-02 4:28 ` [Buildroot] [PATCH 1/1] check-package: avoid false warning of useless flag Ricardo Martincoski
2017-12-02 11:03 ` Yann E. MORIN
2017-12-02 13:10 ` Thomas Petazzoni
2017-12-02 13:54 ` Yann E. MORIN
2017-12-02 14:08 ` Thomas Petazzoni
2017-12-03 17:48 ` Arnout Vandecappelle
2017-12-02 13:52 ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 8/8] gitlab-ci: run check-package Yann E. MORIN
2017-11-30 7:59 ` Thomas Petazzoni
2017-11-30 15:34 ` Yann E. MORIN
2017-12-01 9:54 ` Thomas Petazzoni
2017-12-01 15:23 ` Yann E. MORIN
2017-12-02 4:33 ` Ricardo Martincoski
2017-12-01 22:00 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1054252197.2705387.1512040781069.JavaMail.zimbra@datacom.ind.br \
--to=ricardo.martincoski@datacom.ind.br \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox