buildroot.busybox.net archive mirror
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: buildroot@buildroot.org
Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 0/4] package/pkg-kconfig: introduce generic help (branch yem/kconfig-help)
Date: Sat, 24 Jul 2021 23:19:20 +0200	[thread overview]
Message-ID: <cover.1627161553.git.yann.morin.1998@free.fr> (raw)

Hello All!

This is a counter-proposal to an eariler patch from Thomas, which adds
and fixes help entries for kconfig packages:

    https://patchwork.ozlabs.org/project/buildroot/patch/20210703194001.693553-1-thomas.petazzoni@bootlin.com/

Compared to that patch, this series ointroduces a generic help generator
for kconfig packages, and removes all existing custom help commands for
those packages.

As a cherry on the cake, it adds a new configurator to uClibc, which as
supported nconfig for some time now...

Regards,
Yann E. MORIN.


----------------------------------------------------------------
Yann E. MORIN (4):
      package/pkg-kconfig: move defaults before calling pkg-generic
      package/pkg-kconfig: generate generic help
      package: use the generic _HELP_CMDS for kconfig-based packages
      package/uclibc: add nconfig as a kconfig editor

 boot/barebox/barebox/barebox.mk         |  5 -----
 boot/uboot/uboot.mk                     |  6 -----
 docs/manual/adding-packages-kconfig.txt |  3 +++
 linux/linux.mk                          |  7 ------
 package/busybox/busybox.mk              |  5 +----
 package/pkg-kconfig.mk                  | 40 ++++++++++++++++++++++++++-------
 package/uclibc/uclibc.mk                |  5 +----
 7 files changed, 37 insertions(+), 34 deletions(-)

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

             reply	other threads:[~2021-07-24 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 21:19 Yann E. MORIN [this message]
2021-07-24 21:19 ` [Buildroot] [PATCH 1/4] package/pkg-kconfig: move defaults before calling pkg-generic Yann E. MORIN
2021-07-24 21:19 ` [Buildroot] [PATCH 2/4] package/pkg-kconfig: generate generic help Yann E. MORIN
2021-07-25 13:19   ` Arnout Vandecappelle
2021-07-24 21:19 ` [Buildroot] [PATCH 3/4] package: use the generic _HELP_CMDS for kconfig-based packages Yann E. MORIN
2021-07-24 21:19 ` [Buildroot] [PATCH 4/4] package/uclibc: add nconfig as a kconfig editor Yann E. MORIN
2021-08-05 10:03   ` Peter Korsgaard
2021-07-25 13:21 ` [Buildroot] [PATCH 0/4] package/pkg-kconfig: introduce generic help (branch yem/kconfig-help) Arnout Vandecappelle

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=cover.1627161553.git.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=patrickdepinguin@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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;
as well as URLs for NNTP newsgroup(s).