All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] *config: improve handling of BR2_LEGACY
Date: Sat, 11 Apr 2015 01:43:26 +0200	[thread overview]
Message-ID: <5528601E.2080302@mind.be> (raw)
In-Reply-To: <1428525388-24739-1-git-send-email-yann.morin.1998@free.fr>

On 08/04/15 22:36, Yann E. MORIN wrote:
> From: Arnout Vandecappelle <arnout@mind.be>
> 
> In 8a46d4bf1f the randpackageconfig and allpackageyesconfig were
> extended with disabling all the legacy options, otherwise the resulting
> config couldn't be built. However, that didn't work for randconfig and
> allyesconfig.
> 
> This commit reverts 8a46d4bf1f and replaces it with a different
> approach: skipping of the legacy config options is passed explicitly
> through the environment variable SKIP_LEGACY, which forces
> BR2_SKIP_LEGACY to y.
> 
> We add a (silent) call to olddefconfig to set out the old legacy
> options aside.

 Yes, that's another way to avoid the 'make oldconfig' problem.

 I actually found it useful to have the option user-visible, because then it's
possible to get rid of all of them in one shot. But on the other hand, it's not
so nice that it gets saved in the defconfig...


> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> [yann.morin.1998 at free.fr: do not rely on a user-visible option, works
>  perfectly well with only blind options set from the environment]
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> 
> ---
> Changes v2 -> v3:
>   - add the missing pieces (calling olddefconfig)
> 
> Changes v1 -> v2:
>   - don't use a user-visible option  (Yann)
> ---
>  Config.in.legacy | 12 ++++++++++++
>  Makefile         | 27 ++++++++++++++-------------
>  2 files changed, 26 insertions(+), 13 deletions(-)
> 
> diff --git a/Config.in.legacy b/Config.in.legacy
> index 445cab7..38fca09 100644
> --- a/Config.in.legacy
> +++ b/Config.in.legacy
> @@ -52,6 +52,16 @@
>  #
>  # [End of example]
>  
> +config BR2_SKIP_LEGACY_ENV
> +	bool
> +	option env="SKIP_LEGACY"

 This additional option is no longer needed if it's not user visible.


 v4 coming up.


 Regards,
 Arnout

> +
> +config BR2_SKIP_LEGACY
> +	bool
> +	default y if BR2_SKIP_LEGACY_ENV
> +
> +if !BR2_SKIP_LEGACY
> +
>  config BR2_LEGACY
>  	bool
>  	help
[snip]


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-04-10 23:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 20:36 [Buildroot] [PATCHv3] *config: improve handling of BR2_LEGACY Yann E. MORIN
2015-04-10 23:43 ` Arnout Vandecappelle [this message]
2015-04-11  8:15   ` 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=5528601E.2080302@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.