From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] dash: bump to version 0.5.8-1
Date: Wed, 08 Oct 2014 16:16:51 -0300 [thread overview]
Message-ID: <54358DA3.1030103@zacarias.com.ar> (raw)
In-Reply-To: <87y4sqbds4.fsf@dell.be.48ers.dk>
On 10/08/2014 03:46 PM, Peter Korsgaard wrote:
> But a buildroot config without busybox is quite unlikely.
Well that's what i'm testing here and other than the other patches
that's the only big broken thing that i've found.
For a basic boot the required packages are:
coreutils -> cat, echo, and a ton of other tiny utils
net-tools -> hostname, ifconfig and such
util-linux (agetty, fsck, kill, login utils, mount/umount)
some shell (bash, dash, zsh)
Optional but nice:
sysklogd -> a logger, not strictly necessary but convenient.
procps-ng -> ps utils.
and many others for the usual complete shell experience.
Not covered yet:
ifdown/ifup - we can package it.
start-stop-daemon - we can probably get away without it by tweaking
initscripts.
The problem is that we allow busybox to be turned off for
systemv/systemd so we've gotta cover those use cases.
> > It's possible, probably best in System Configuration an option that
> > selects the appropiate package.
> > I wouldn't pull in busybox though, only make the option available if
> > BR2_PACKAGE_BUSYBOX.
> > And make the symlink in target-finalize to avoid touching the packages
> > much (actually making them simpler).
>
> Yes, we can do something like that if there's interest / need. I
> personally don't care enough about it do it myself, but I do want
> reproducible builds.
>
> A real config with multiple (non busybox) shells is imho quite unlikely
> though.
I'll give it a shot, it shouldn't be hard.
Yes it would be odd for multiple non-busybox shells to exist, that was
my reasoning that any full shell would step on /bin/sh, see? ;)
> Sure it is arbitrary, but that's what we have today and I haven't heard
> anybody complaining.
Well, we can evolve it a bit, once the selection option is done it will
be quite easy to add new shell options which, contrary to adding a ton
of ifeqs, is nicer.
It might be interesting in the long run since we'll have to deal with
/etc/shells (not quite the same but still in the same area) for
non-busybox scenarios.
Regards.
next prev parent reply other threads:[~2014-10-08 19:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 13:19 [Buildroot] [PATCH 1/5] dash: bump to version 0.5.8-1 Gustavo Zacarias
2014-10-08 13:19 ` [Buildroot] [PATCH 2/5] zsh: security bump to version 5.0.7 Gustavo Zacarias
[not found] ` <87a956eadv.fsf@dell.be.48ers.dk>
2014-10-08 17:36 ` Gustavo Zacarias
2014-10-08 18:42 ` Peter Korsgaard
2014-10-12 10:50 ` Peter Korsgaard
2014-10-08 13:19 ` [Buildroot] [PATCH 3/5] bash: minor install tweaks Gustavo Zacarias
2014-10-08 17:32 ` Peter Korsgaard
2014-10-08 13:19 ` [Buildroot] [PATCH 4/5] procps-ng: bump to version 3.3.10 Gustavo Zacarias
2014-10-08 17:32 ` Peter Korsgaard
2014-10-08 13:19 ` [Buildroot] [PATCH 5/5] sysklogd: security bump to version 1.5.1 Gustavo Zacarias
2014-10-08 17:36 ` Peter Korsgaard
2014-10-08 17:27 ` [Buildroot] [PATCH 1/5] dash: bump to version 0.5.8-1 Peter Korsgaard
2014-10-08 17:29 ` Gustavo Zacarias
2014-10-08 18:05 ` Peter Korsgaard
2014-10-08 18:21 ` Gustavo Zacarias
2014-10-08 18:46 ` Peter Korsgaard
2014-10-08 19:16 ` Gustavo Zacarias [this message]
2014-10-11 14:28 ` Arnout Vandecappelle
2014-10-12 10:50 ` Peter Korsgaard
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=54358DA3.1030103@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