All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 00/13] Improve alphabetical order checking of Config.in files
Date: Mon, 7 Oct 2019 23:59:54 +0200	[thread overview]
Message-ID: <1d755944-b97c-27df-9e81-cdf96c310bda@mind.be> (raw)
In-Reply-To: <20191005122227.7297-1-jerzy.m.grzegorek@gmail.com>



On 05/10/2019 14:22, Jerzy Grzegorek wrote:
> The main purpose of this patch series is to improve alphabetical order
> checking of comments, menus and packages in Config.in files.
> Patches 1-6 are preliminary ones and add small improvements.
> Patches 7, 9, 10 do the main work.
> Patches 8, 11-13 fix issues in Config.in files.
> 
> Changes v1 -> v2:
>   - change the subject prefix checkpackagelib/lib_config.py to utils/checkpackagelib
>     in all patches (Ricardo)
>   - drop patch: 
>     utils/checkpackagelib: CommentsMenusPackagesOrder: drop function get_line (Ricardo) 
>   - use package arrays initialize in before() (Ricardo)
>   - improve the commit message of patch 5 (Ricardo)
> 
> Regards,
> Jerzy
> 
> Jerzy Grzegorek (13):
>   utils/checkpackagelib: CommentsMenusPackagesOrder: remove '-comment'
>     state before the '-menu' one
>   utils/checkpackagelib: CommentsMenusPackagesOrder: separate the lines
>     support
>   utils/checkpackagelib: CommentsMenusPackagesOrder: use '-' to describe
>     state
>   utils/checkpackagelib: CommentsMenusPackagesOrder: use package arrays
>     initialize in before()
>   utils/checkpackagelib: CommentsMenusPackagesOrder: initialize
>     'menu_of_packages' array

 I applied these to master, sometimes with small improvements to the commit message.

>   utils/checkpackagelib: CommentsMenusPackagesOrder: add more Config.in
>     files to check

 I applied this one as well, with one exception: I removed boot/Config.in
because it is currently NOT correctly sorted (arm-trusted-firmware should come
before the at91 packages).

 Just for kicks, I removed the whitelist entirely and ran check-package on all
Config.in files. It turned up quite a few errors still, and some of these are in
fact relevant (in qt5 and in toolchain-external). So I'm thinking, it may be
useful to turn the whitelist into a blacklist (after fixing the incorrect
ordering, of course). And instead of maintaining the blacklist in
checkpackagelib, it is probably better to do it with comments in the files
themselves:

# CommentsMenusPackagesOrder off


and set some class variable to False if that comment is found.

 There are a few menus where we can still bikeshed on the proper ordering, e.g.
gstreamer1.


>   utils/checkpackagelib: CommentsMenusPackagesOrder: check package
>     ordering just before 'if ' statement

 These and the following I have marked as Rejected in patchwork as I believe we
shouldn't do this kind of check automatically.

 Regards,
 Arnout

>   package/Config.in: fix packages ordering
>   utils/checkpackagelib: CommentsMenusPackagesOrder: check the order of
>     comments menu
>   utils/checkpackagelib: CommentsMenusPackagesOrder: check the order of
>     menu of menus
>   package/Config.in: fix menus ordering
>   package/kodi/Config.in: fix menus ordering
>   package/kodi/Config.in: fix menus ordering
> 
>  package/Config.in                   |  58 ++++++------
>  package/kodi/Config.in              |  12 +--
>  utils/checkpackagelib/lib_config.py | 133 ++++++++++++++++++++++++----
>  3 files changed, 150 insertions(+), 53 deletions(-)
> 

      parent reply	other threads:[~2019-10-07 21:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05 12:22 [Buildroot] [PATCH v2 00/13] Improve alphabetical order checking of Config.in files Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 01/13] utils/checkpackagelib: CommentsMenusPackagesOrder: remove '-comment' state before the '-menu' one Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 02/13] utils/checkpackagelib: CommentsMenusPackagesOrder: separate the lines support Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 03/13] utils/checkpackagelib: CommentsMenusPackagesOrder: use '-' to describe state Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 04/13] utils/checkpackagelib: CommentsMenusPackagesOrder: use package arrays initialize in before() Jerzy Grzegorek
2019-10-06 23:52   ` Ricardo Martincoski
2019-10-05 12:22 ` [Buildroot] [PATCH v2 05/13] utils/checkpackagelib: CommentsMenusPackagesOrder: initialize 'menu_of_packages' array Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 06/13] utils/checkpackagelib: CommentsMenusPackagesOrder: add more Config.in files to check Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 07/13] utils/checkpackagelib: CommentsMenusPackagesOrder: check package ordering just before 'if ' statement Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 08/13] package/Config.in: fix packages ordering Jerzy Grzegorek
2019-10-05 13:30   ` Arnout Vandecappelle
2019-10-05 15:23     ` Jerzy Grzegorek
2019-10-07 21:03       ` Arnout Vandecappelle
2019-10-05 12:22 ` [Buildroot] [PATCH v2 09/13] utils/checkpackagelib: CommentsMenusPackagesOrder: check the order of comments menu Jerzy Grzegorek
2019-10-05 13:35   ` Arnout Vandecappelle
2019-10-05 12:22 ` [Buildroot] [PATCH v2 10/13] utils/checkpackagelib: CommentsMenusPackagesOrder: check the order of menu of menus Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 11/13] package/Config.in: fix menus ordering Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 12/13] package/kodi/Config.in: " Jerzy Grzegorek
2019-10-05 12:22 ` [Buildroot] [PATCH v2 13/13] " Jerzy Grzegorek
2019-10-07 21:59 ` Arnout Vandecappelle [this message]

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=1d755944-b97c-27df-9e81-cdf96c310bda@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.