From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] utils/checkpackagelib: exclude two files from Config.in indentation check
Date: Tue, 19 Dec 2017 09:36:14 +0100 [thread overview]
Message-ID: <20171219093614.24bdc185@windsurf> (raw)
In-Reply-To: <5a3871cd6f3a9_bd01603ab4851a3@ultri3.mail>
Hello,
On Mon, 18 Dec 2017 23:56:29 -0200, Ricardo Martincoski wrote:
> On Mon, Dec 18, 2017 at 06:43 AM, Thomas Petazzoni wrote:
>
> > package/x11r7/Config.in and package/kodi/Config.in do not comply with
> > the normal Config.in indentation rules. However, this violation of the
> > rule is legitimate, so let's skip them in check-package for this
> > specific indentation check.
> >
> > This removes the last 314 remaining warnings on Config.in files.
>
> There are also 7 warnings for Config.in.host
> They can obviously be fixed in another patch(es).
Ah, right, forgot about Config.in.host.
> After this/these we can add
> -o -name 'Config.in'
> or
> -o -name 'Config.*'
> to the check-package job in the gitlab yml, but I guess it is your plan already.
This is obviously the plan.
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> >
> > ---
> > Note: I am not totally sure about this patch. Indeed package/Config.in
> > uses the same rule as package/{x11r7,kodi}/Config.in, but
> > check-package doesn't report warnings about it. Perhaps I'm missing
> > something in the check-package logic.
>
> See FILE_IS_FROM_A_PACKAGE in the main script.
> I first limited the script to files in the package directory because there are
> a lot of false warnings from other directories, many of them for historical
> reasons. And... well... it also named check-"package".
> I planned to expand it first to boot, then to to linux and toolchain, but I
> didn't get to it yet.
Ah, ok, makes sense. I think we will progressively want to extend it
indeed, starting first with bootloaders, linux and toolchain as you
suggest.
> > + if self.filename in [ "./package/x11r7/Config.in",
> > + "./package/kodi/Config.in" ]:
>
> The 4 warnings from flake8 already in the file I plan to fix in a series for
> all flake8 warnings in the tree (those 4 actually adding '# noqa' since
> check-package uses 'inspect' to know which check functions to run).
>
> But (in the case you stick to this solution, see the other e-mail) could you
> fix those 2 new warnings?
> utils/checkpackagelib/lib_config.py:137:38: E201 whitespace after '['
> utils/checkpackagelib/lib_config.py:138:65: E202 whitespace before ']'
ACK. I don't use flake8, so I don't notice such warnings. I'll fix and
resend if we agree that this is the appropriate solution.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-19 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 8:43 [Buildroot] [PATCH] utils/checkpackagelib: exclude two files from Config.in indentation check Thomas Petazzoni
2017-12-18 22:03 ` Yann E. MORIN
2017-12-19 1:57 ` Ricardo Martincoski
2017-12-19 5:33 ` Bernd Kuhls
2017-12-19 8:28 ` Thomas Petazzoni
2017-12-20 11:06 ` Yann E. MORIN
2017-12-19 1:56 ` Ricardo Martincoski
2017-12-19 8:36 ` Thomas Petazzoni [this message]
2017-12-19 23:32 ` Ricardo Martincoski
2017-12-20 8:10 ` Thomas Petazzoni
2018-03-22 3:20 ` Ricardo Martincoski
2018-03-22 8:18 ` 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=20171219093614.24bdc185@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--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