From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] busybox: preserve ncurses progs/tools
Date: Thu, 20 Apr 2017 09:20:15 +0200 [thread overview]
Message-ID: <20170420092015.3b2f7fbd@free-electrons.com> (raw)
In-Reply-To: <4e5df153-6f58-8b65-faf4-f87fb91324cd@mind.be>
Hello,
On Fri, 14 Apr 2017 19:00:32 +0200, Arnout Vandecappelle wrote:
> This is the correct approach I think. I think we could also do this for all the
> other cases where we have a -> busybox dependency just because they install the
> same apps.
Yes, I'm also wondering if it isn't better to disable the Busybox
applets (like Matt does in this patch for ncurses) rather then
overwriting the symlinks.
First of all, overwriting the symlinks means that if you "make
busybox-reinstall", you no longer get the right thing (for sure, we
never guarantee that partial builds/rebuilds give the correct output,
but it's nice when they do). And then of course, it means that there is
code in Busybox, consuming some space, that is never used.
The only annoyance that I can see is a potential blotification of
busybox.mk, with lots of conditional for various packages.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-20 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 3:20 [Buildroot] [PATCH 1/1] busybox: preserve ncurses progs/tools Matt Weber
2017-04-14 8:59 ` Thomas Petazzoni
2017-04-24 19:29 ` Peter Korsgaard
2017-04-14 17:00 ` Arnout Vandecappelle
2017-04-14 18:27 ` Arnout Vandecappelle
2017-04-20 7:20 ` Thomas Petazzoni [this message]
2017-04-20 12:03 ` Danomi Manchego
2017-04-23 18:03 ` Peter Korsgaard
2017-04-23 20:55 ` Arnout Vandecappelle
2017-04-24 15:36 ` Danomi Manchego
2017-04-24 20:03 ` Arnout Vandecappelle
2017-04-24 19:29 ` Peter Korsgaard
2017-04-24 20:59 ` Arnout Vandecappelle
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=20170420092015.3b2f7fbd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.