Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 10 Mar 2016 21:20:34 +0100	[thread overview]
Message-ID: <20160310202033.GA3424@free.fr> (raw)
In-Reply-To: <20160310093115.6ff24ea6@free-electrons.com>

Thomas, All,

On 2016-03-10 09:31 +0100, Thomas Petazzoni spake thusly:
> On Thu, 10 Mar 2016 00:35:03 +0100, Arnout Vandecappelle wrote:
> 
> > > 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 bit I really like!
> 
> Doesn't Yann proposal fails short if you want to pretty print something
> like this:
> 
> 	foobar - This is a really really long help message that spans
> 	         multiple lines, and would definitely be too long on
> 	         one single line.

Indeed, it was no longer possible with the patchset I posted (which was
just hacked around quickly), but it's fixed locally.

> IOW, I believe we should leave more freedom to what is appended to the
> help text, and simply leave it to the person writing the help text to
> format it properly.

Well, the first patch in my series is just that: expost a new hel prule
that the user is *entirely* free to implement on his own. The macro is
just an added bonus.

Basically, if all one wants is to display help for br2-external or other
such customisations, then the first patch in my series was entirely
sufficient. It is addressing my concenr about mixing our help with
custom help.

On the other hand, patches 2 onweard were addressing the second patch in
J?r?me's series, which was moving packages' specific help into the
corresponding packages. It has nothing to do with providing custom help,
althgouh custom help may (anmd it's only a 'may') use that macro, of
course.

> In my opinion, the very simple proposal from J?r?me has turned into a
> much more complicated solution, with no real benefit.

Well, I have two concerns about that series:
 1- the mixing of internal and custom help,
 2- the way it is implemented looks ugly to me.

And I doubt my own proposal is very complex. Sure, there are two trivial
shell expansions, that are even POSIX and not bashisms. Compared to
other dirty tricks we do in a lot of other places, those are hardly
black magic...

Regards,
Yann E. MORIN.

> Best regards,
> 
> Thomas
> -- 
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-03-10 20:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 22:22 [Buildroot] [PATCH 0/8] core: allow for custom, local help; rearrange package-specific help (branch yem/help) Yann E. MORIN
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 [this message]
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=20160310202033.GA3424@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