From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Rebuild busybox when an external config is updated
Date: Fri, 02 May 2014 10:21:34 -0300 [thread overview]
Message-ID: <53639BDE.4050009@zacarias.com.ar> (raw)
In-Reply-To: <87ha58corn.fsf@steelpick.2x.cz>
On 05/02/2014 10:07 AM, Michal Sojka wrote:
> I could definitely live with this conclusion, but on the other hand I
> don't think that adding one more dependency is being "too smart". What
> are the drawbacks of adding this functionality? If it is just adding the
> same to other packages, I'm willing to do that. Quick grep suggests that
> only the following packages have custom config files: at91bootstrap3.mk,
> barebox.mk, ubi.mk, linux.mk, busybox.mk, freetype.mk, luarocks.mk,
> qt.mk, uclibc.mk.
Hi.
I think i've already mentioned it in the past, but here it goes again.
Because you'd need a full rebuild of packages that depend on busybox as
well since we use DEPENDENCIES to make packages with superior
functionality to that provided by busybox build afterwards to override
it's functionality (logic = it's YES and better so do it).
If you rebuild busybox without doing so for the other packages then your
"reproducibly" goes down the drain since the "big and featured" binaries
get overwritten by busybox (with the way busybox is installed at the
moment) for a built project.
Regards.
next prev parent reply other threads:[~2014-05-02 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 20:05 [Buildroot] [PATCH] Rebuild busybox when an external config is updated Michal Sojka
2014-05-01 19:46 ` Thomas De Schampheleire
2014-05-01 20:31 ` Yann E. MORIN
2014-05-02 13:07 ` Michal Sojka
2014-05-02 13:21 ` Gustavo Zacarias [this message]
2014-05-02 14:59 ` Danomi Manchego
2014-05-02 15:37 ` Michal Sojka
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=53639BDE.4050009@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