Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today
Date: Thu, 24 Jan 2013 07:44:56 +0100	[thread overview]
Message-ID: <5100D868.7070609@mind.be> (raw)
In-Reply-To: <87k3r69vdi.fsf@dell.be.48ers.dk>

On 01/21/13 20:41, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni<thomas.petazzoni@free-electrons.com>  writes:
>
>   Thomas>  Dear Nigel Sollars,
>   Thomas>  On Mon, 21 Jan 2013 12:26:41 -0500, Nigel Sollars wrote:
>
>   >>  Oh I see what your saying, basically the rule is dont use an older
>   >>  config.  I am guess that manually changing the config to the new
>   >>  location in this instance, would be good enough for now..
>
>   Thomas>  No, the rule is more "we should not break existing configurations". But
>   Thomas>  sometimes we do, unfortunately. And in many cases, I am the one
>   Thomas>  responsible for those changes that create incompatibility with existing
>   Thomas>  configurations.
>
>   Thomas>  Arnout recently added a "legacy" mechanism that should, in the
>   Thomas>  future, help in making such changes less painful.
>
> Indeed. It's not perfect, but we do try. I can also recommend to use the
> 'make savedefconfig' feature to create a minimalistic defconfig file
> rather than the full explicit .config, as you will then automatically
> pick up the new defaults for stuff you haven't changed anyway.

  Unfortunately, the defconfig forgets about options that you want 
explicitly at their default value but for which the default has changed. 
BR2_KERNEL_HEADERS_xxx comes to mind.

  But there's absolutely no way to solve that, except by rewriting Kconfig...


  Regards,
  Arnout


-- 
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:[~2013-01-24  6:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 21:03 [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today Nigel Sollars
2013-01-18 23:00 ` Thomas Petazzoni
2013-01-21 17:02   ` Nigel Sollars
2013-01-21 17:11     ` Thomas Petazzoni
2013-01-21 17:26       ` Nigel Sollars
2013-01-21 17:51         ` Thomas Petazzoni
2013-01-21 19:41           ` Peter Korsgaard
2013-01-24  6:44             ` Arnout Vandecappelle [this message]
2013-01-24  6:42           ` Arnout Vandecappelle
2013-01-24 12:44             ` Peter Korsgaard

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=5100D868.7070609@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox