From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] less: build after busybox
Date: Thu, 26 Jul 2012 20:12:18 -0300 [thread overview]
Message-ID: <5011CED2.4060105@zacarias.com.ar> (raw)
In-Reply-To: <CAHXCMM+ORAKWNqQJ34FEZ+AbQ5dfpVuZAF3Y85xz6Wf9pmccmg@mail.gmail.com>
On 07/26/12 19:30, Samuel Martin wrote:
> 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...
>
> At least it would be worth to document which binary works if using the
> one provided by the busybox built instead of the one provided by
> another package, which doesn't.
> This makes echo to some other recent thread about using login from
> util-linux or busybox.
>
>
> Regards,
It's pretty much standard issue in buildroot for busybox command
alternatives that are richer in functionality when they're selected.
If less is in the configuration it's because someone wants it, specially
since it's hidden by the BUSYBOX_SHOW_OTHERS kludge to avoid
big/duplicate alternatives.
Just hit this particular one when testing the ncurses bump, got busybox
less which doesn't use it even though i selected standalone less.
Maybe i don't understand what you mean about build dependency, but it's
the only way at the moment to ensure it's built after busybox in a
simple way.
And it's been done for a ton of other packages already like iproute2,
gawk, grep, sysklogd, usbutils and so on...
Granted that util-linux might have a heavier hand since the options
aren't so granular and there are several binaries with differing
functionality that overlap busybox, but it's a completely different case
than this.
Regards.
next prev parent reply other threads:[~2012-07-26 23:12 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 [this message]
2012-07-26 23:23 ` Samuel Martin
2012-07-27 8:15 ` Arnout Vandecappelle
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=5011CED2.4060105@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