From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/8] core: allow for custom, local help; rearrange package-specific help (branch yem/help)
Date: Wed, 9 Mar 2016 23:22:22 +0100 [thread overview]
Message-ID: <cover.1457561521.git.yann.morin.1998@free.fr> (raw)
Hello All!
This series is an alternative proposal to support displaying custom,
local help, most probably from a br2-external tree (or from a lcal.mk,
but that'd be pretty insane).
The basic idea is to offer the user help entries for local
customisations, but without mixing them with our own help entries.
I believe we want to keep them separate, as inter-mixing the two could
lead users to believe those addtional help entries are "native" in
buildroot, when they are not.
The same way we expose all of br2-external config options under a
sub-menu labelled "User-provided options", we do similarly for the
custom help, albeit with a slight shorter moniker, 'help-local'.
After the first patch implements this (which is really all that is
needed to print custom help), we go further with providing a macro that
pretty-prints the help for rules, so that the layout is all handled in a
single location. This macro can also be used by the local help, too.
This macro is then used to implement per-package specific help (which is
currently only about kconfig-related changes, but can not easily be done
in the kconfig-package infra) into the packages themseves, to clean up
the main help code (the entris are still displayed there, they are just
definedin each concerned package).
All that, plus a bit of associated documentation, of course. ;-)
Thanks to J?r?me for his initial proposal, and Arnout for
before-inception suggestions:
http://lists.busybox.net/pipermail/buildroot/2016-March/155415.html
Regards,
Yann E. MORIN.
The following changes since commit 07f46c2b6daec44a6176039c90be67e66c4c2e42:
package/busybox: support automatic module loading with mdev (2016-03-09 23:07:44 +0100)
are available in the git repository at:
git://git.busybox.net/~ymorin/git/buildroot yem/help
for you to fetch changes up to b94d50a5f7717ad1ea2d9cab129155a0ab203f71:
docs/manual: document the br2-external help-local (2016-03-09 23:10:37 +0100)
----------------------------------------------------------------
Yann E. MORIN (8):
core: add the possibility to provide help for local, custom rules
core/pkg-utils: add a macro to pretty-print a help entry
core/pkg-generic: add help about package-specific rules
package/busybox: use the generic help rules
linux: add the generic help rules
package/uclibc: use the generic help rules
boot/barebox: use the generic help rules
docs/manual: document the br2-external help-local
Makefile | 23 +++++++----------------
boot/barebox/barebox.mk | 4 ++++
docs/manual/adding-packages-generic.txt | 6 ++++++
docs/manual/customize-outside-br.txt | 20 ++++++++++++++++++++
linux/linux.mk | 6 ++++++
package/busybox/busybox.mk | 2 ++
package/pkg-generic.mk | 2 ++
package/pkg-utils.mk | 13 +++++++++++++
package/uclibc/uclibc.mk | 2 ++
9 files changed, 62 insertions(+), 16 deletions(-)
--
.-----------------.--------------------.------------------.--------------------.
| 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 reply other threads:[~2016-03-09 22:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 22:22 Yann E. MORIN [this message]
2016-03-09 22:22 ` [Buildroot] [PATCH 1/8] core: add the possibility to provide help for local, custom rules Yann E. MORIN
2016-03-09 23:35 ` Arnout Vandecappelle
2016-03-10 20:22 ` Yann E. MORIN
2016-03-11 0:01 ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 2/8] core/pkg-utils: add a macro to pretty-print a help entry Yann E. MORIN
2016-03-09 23:37 ` Arnout Vandecappelle
2016-03-10 9:31 ` Jérôme Pouiller
2016-03-10 20:27 ` Yann E. MORIN
2016-03-10 20:24 ` Yann E. MORIN
2016-03-09 22:22 ` [Buildroot] [PATCH 3/8] core/pkg-generic: add help about package-specific rules Yann E. MORIN
2016-03-09 23:38 ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 4/8] package/busybox: use the generic help rules Yann E. MORIN
2016-03-09 23:38 ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 5/8] linux: add " Yann E. MORIN
2016-03-09 23:47 ` Arnout Vandecappelle
2016-03-10 9:21 ` Jérôme Pouiller
2016-03-10 9:39 ` Thomas Petazzoni
2016-03-10 9:52 ` Arnout Vandecappelle
2016-03-10 10:12 ` Thomas Petazzoni
2016-03-10 20:34 ` Yann E. MORIN
2016-03-10 20:58 ` Thomas Petazzoni
2016-03-10 20:29 ` Yann E. MORIN
2016-03-09 22:22 ` [Buildroot] [PATCH 6/8] package/uclibc: use " Yann E. MORIN
2016-03-09 23:47 ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 7/8] boot/barebox: " Yann E. MORIN
2016-03-09 23:47 ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 8/8] docs/manual: document the br2-external help-local Yann E. MORIN
2016-03-09 23:35 ` [Buildroot] [PATCH 0/8] core: allow for custom, local help; rearrange package-specific help (branch yem/help) Arnout Vandecappelle
2016-03-10 8:31 ` Thomas Petazzoni
2016-03-10 20:20 ` Yann E. MORIN
2016-03-10 21:01 ` 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=cover.1457561521.git.yann.morin.1998@free.fr \
--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