Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] coreutils: belongs to system tools, not development
Date: Tue, 03 Dec 2013 11:32:53 +0100	[thread overview]
Message-ID: <87pppens16.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <529DAFA0.9030903@zacarias.com.ar> (Gustavo Zacarias's message of "Tue, 03 Dec 2013 07:17:04 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

 > On 12/03/2013 05:08 AM, Jeremy Rosen wrote:
 >> I personally don't know exactly what busybox provides, this option is
 >> a simple way to make sure I don't compile any useless stuff...
 >> 
 >> I'm in favor of keeping it or provide another way to find duplicates

 > Sometimes the busybox version is short of features and you need the full
 > version even when keeping busybox around.

Exactly, like we're hiding bash/zsh even though the differences from
busybox ash are pretty huge. Same for syslogd/sysvinit or vim.

 > With that being said you sometimes want to avoid the opposite too. On
 > this patchset i've found there are many of the big packages required
 > (and needed fixing) to get a nice (no warnings or error messages)
 > booting system with the default skeleton, OTOH: coreutils, util-linux,
 > some shell (bash), sysvinit, sysklogd, linux-pam (inherent for util-linux).
 > And with those we still get a warning from util-linux's hostname not
 > being feature complete (oh the irony, busybox hostname is, we need
 > net-tools to replace it).
 > And we're still lacking ifup/ifdown :)

Which relate to the point about these options not getting a lot of
testing.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-12-03 10:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 10:49 [Buildroot] [PATCH 1/5] coreutils: belongs to system tools, not development Gustavo Zacarias
2013-12-02 10:49 ` [Buildroot] [PATCH 2/5] coreutils: bump to version 8.21 Gustavo Zacarias
2013-12-03  8:07   ` Peter Korsgaard
2013-12-02 10:49 ` [Buildroot] [PATCH 3/5] util-linux: add agetty->getty symlink Gustavo Zacarias
2013-12-03  8:08   ` Peter Korsgaard
2013-12-02 10:49 ` [Buildroot] [PATCH 4/5] zsh: alpha sort menu option Gustavo Zacarias
2013-12-03  8:09   ` Peter Korsgaard
2013-12-03  8:50     ` Thomas Petazzoni
2013-12-03 10:23       ` Gustavo Zacarias
2013-12-03 10:28         ` Peter Korsgaard
2013-12-03 10:28       ` Peter Korsgaard
2013-12-02 10:49 ` [Buildroot] [PATCH 5/5] sysklogd: install to /sbin Gustavo Zacarias
2013-12-03  8:12   ` Peter Korsgaard
2013-12-03  8:01 ` [Buildroot] [PATCH 1/5] coreutils: belongs to system tools, not development Peter Korsgaard
2013-12-03  8:08   ` Jeremy Rosen
2013-12-03 10:17     ` Gustavo Zacarias
2013-12-03 10:32       ` Peter Korsgaard [this message]
2013-12-03  8:59   ` Thomas Petazzoni
2013-12-03 10:05     ` Peter Korsgaard
2013-12-03 10:12       ` Thomas Petazzoni
2013-12-03 10:34         ` Peter Korsgaard
2013-12-03 10:08     ` Gustavo Zacarias

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=87pppens16.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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