From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core/help: fix custom help without a .config
Date: Tue, 22 Mar 2016 23:52:39 +0100 [thread overview]
Message-ID: <20160322235239.7a75f515@free-electrons.com> (raw)
In-Reply-To: <56F1C9D1.2010104@mind.be>
Hello,
On Tue, 22 Mar 2016 23:40:17 +0100, Arnout Vandecappelle wrote:
> On 03/20/16 22:24, Yann E. MORIN wrote:
> > When there is no .config, we do not source $(BR2_EXTERNAL)/external.mk.
> > So we can not expose the custom help in that situation.
> >
> > It is now known whether sourcing $(BR2_EXTERNAL)/external.mk outside the
> > HAVE_DOT_CONFIG conditional block is entirely safe. Even if it would
> > work today, we would have a hard time not breaking it in the future,
> > because we do not have automatic checks for that and would need to rely
> > on users reporting issues after the fact.
> >
> > Instead, we require the custom help to be defined in its own file in the
> > br2-external tree. This way, we can safely include it unconditionally.
>
> IMHO that custom help was a bad idea. It's adding complexity, an extra file in
> BR2_EXTERNAL, and really not that useful...
Agreed. I'm not sure it's worth it. It's still time to revert if we
don't think it's a good idea. Peter?
Without this custom help thing, it is already possible to define some
custom make target in external.mk that will display some help. It won't
be available until a configuration is defined, but oh well, who reads
help texts anyway?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-22 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 21:24 [Buildroot] [PATCH] core/help: fix custom help without a .config Yann E. MORIN
2016-03-22 22:40 ` Arnout Vandecappelle
2016-03-22 22:52 ` Thomas Petazzoni [this message]
2016-04-15 22:16 ` Peter Korsgaard
2016-04-16 7:28 ` Thomas Petazzoni
2016-04-16 21:07 ` Yann E. MORIN
2016-04-17 22:51 ` Arnout Vandecappelle
2016-04-18 20:27 ` Yann E. MORIN
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=20160322235239.7a75f515@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.