Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] Rebuild packages when their external config is updated
Date: Fri, 16 May 2014 13:26:08 -0300	[thread overview]
Message-ID: <53763C20.1050408@zacarias.com.ar> (raw)
In-Reply-To: <1400253776-21759-2-git-send-email-sojka@merica.cz>

On 05/16/2014 12:22 PM, Michal Sojka wrote:

> Packages like busybox, Linux kernel or uclibc can "import" their
> configuration files from external location specified either in
> buildroot's .config or in an environment variable. Currently, this
> import happens only when the package is built for the first time. When
> the external config changes later, the package is not rebuilt with the
> updated configuration until the corresponding .stamp_configured file
> is manually deleted. This patch changes this to automatically rebuild
> the package, when its external configuration files is newer than
> .stamp_configured.

This is an extremely bad idea for uclibc, ABI compatibility is not
guaranteed and changes to the configuration make it change in
incompatible ways, hence you'd need to rebuild everything if this happens.
Unless i'm missing something you're not considering this scenario.
Regards.

  reply	other threads:[~2014-05-16 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 15:22 [Buildroot] [PATCH v2 0/1] Rebuild packages when their external config is updated Michal Sojka
2014-05-16 15:22 ` [Buildroot] [PATCH v2 1/1] " Michal Sojka
2014-05-16 16:26   ` Gustavo Zacarias [this message]
2014-05-16 21:18   ` Yann E. MORIN
2014-07-29 19:38   ` Thomas Petazzoni
2014-07-29 20:39     ` Thomas De Schampheleire

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=53763C20.1050408@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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