From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] less: build after busybox
Date: Fri, 27 Jul 2012 10:15:52 +0200 [thread overview]
Message-ID: <50124E38.6040504@mind.be> (raw)
In-Reply-To: <CAHXCMM+ORAKWNqQJ34FEZ+AbQ5dfpVuZAF3Y85xz6Wf9pmccmg@mail.gmail.com>
On 07/27/12 00:30, Samuel Martin wrote:
>> > +# Build after busybox, full-blown is better
>> > +LESS_DEPENDENCIES = ncurses $(if $(BR2_PACKAGE_BUSYBOX),busybox)
> Though I understand why you prefer this one, I somehow don't really
> like it... because it's not about build dependency, but build/install
> order...
I also don't really like it. For instance, if you rebuild busybox, this
will not trigger a reinstall of less so it will again be the busybox version
that prevails...
However, I don't see a better solution than this one. For sure,
selecting less and getting busybox is worse than this.
One alternative could be to automatically deselect less from busybox
when the full-blown less is selected. But also that is a bit complex
I think.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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
next prev parent reply other threads:[~2012-07-27 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 19:18 [Buildroot] [PATCH] less: build after busybox Gustavo Zacarias
2012-07-26 22:30 ` Samuel Martin
2012-07-26 23:12 ` Gustavo Zacarias
2012-07-26 23:23 ` Samuel Martin
2012-07-27 8:15 ` Arnout Vandecappelle [this message]
2012-07-27 10:26 ` Gustavo Zacarias
2012-07-27 10:30 ` Thomas Petazzoni
2012-07-31 14:30 ` Arnout Vandecappelle
2012-07-30 17:23 ` Thomas Petazzoni
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=50124E38.6040504@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