Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Full config files for each board are yucky.
Date: Mon, 19 Jul 2010 07:15:49 +0200	[thread overview]
Message-ID: <87hbjwuk56.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTimWP0NejW9l0IQSazcaldVaJu0dySV8bGsqh3Wo@mail.gmail.com> (Mitch Davis's message of "Mon, 19 Jul 2010 12:29:36 +1000")

>>>>> "Mitch" == Mitch Davis <mjd+buildroot@afork.com> writes:

Hi,

 Mitch> <rant>That *every* defconfig file needs to be changed indicates a
 Mitch> failing of the present system, where we have pre-canned config files
 Mitch> for every board, that need ongoing maintenance whenever something in
 Mitch> the Kconfig files change.</rant>

Agreed, I was thinking of running Uwe's reduce script:

http://lkml.org/lkml/2010/7/13/134

 Mitch> I have an alternative config system where every board inherits config
 Mitch> options from something else (ultimately the defaults in the config
 Mitch> system), then a board can turn on and off and set options which are
 Mitch> relevant to that board.  BR2_GIT would only need to be changed in one
 Mitch> place, if at all.  I'll clean it up and publish it, if anyone's
 Mitch> interested...

What would that buy us compared to Uwe's script? Would that involve
significant changes to package/config making updates harder?

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2010-07-19  5:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19  2:29 [Buildroot] Full config files for each board are yucky Mitch Davis
2010-07-19  5:15 ` Peter Korsgaard [this message]

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=87hbjwuk56.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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