From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] utils/checkpackagelib: exclude two files from Config.in indentation check
Date: Mon, 18 Dec 2017 23:03:44 +0100 [thread overview]
Message-ID: <20171218220344.GC2903@scaer> (raw)
In-Reply-To: <20171218084303.12472-1-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2017-12-18 09:43 +0100, Thomas Petazzoni spake thusly:
> 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.
Can't we simply fix those two files to not have that unusual indentation
in the first place?
AFAICS, that special indentation is about the 'source' lines... Surely
that does not bring much to have them indented, and they could simply be
left-aligned...
Regards,
Yann E. MORIN.
> This removes the last 314 remaining warnings on Config.in files.
>
> 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.
> ---
> utils/checkpackagelib/lib_config.py | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/utils/checkpackagelib/lib_config.py b/utils/checkpackagelib/lib_config.py
> index 26ebb393d1..fb39182b91 100644
> --- a/utils/checkpackagelib/lib_config.py
> +++ b/utils/checkpackagelib/lib_config.py
> @@ -133,6 +133,10 @@ class Indent(_CheckFunction):
> text]
> elif entry in entries_that_should_not_be_indented:
> if not text.startswith(entry):
> + # two Config.in files have a special but legitimate indentation rule
> + if self.filename in [ "./package/x11r7/Config.in",
> + "./package/kodi/Config.in" ]:
> + return
> return ["{}:{}: should not be indented"
> .format(self.filename, lineno),
> text]
> --
> 2.14.3
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-12-18 22:03 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 [this message]
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
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=20171218220344.GC2903@scaer \
--to=yann.morin.1998@free.fr \
--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