Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] dash: bump to version 0.5.8-1
Date: Sat, 11 Oct 2014 16:28:05 +0200	[thread overview]
Message-ID: <54393E75.2090206@mind.be> (raw)
In-Reply-To: <54358DA3.1030103@zacarias.com.ar>

On 08/10/14 21:16, Gustavo Zacarias wrote:
> On 10/08/2014 03:46 PM, Peter Korsgaard wrote:
> 
[snip]
>>  > 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? ;)

 Hi Gustavo,

 We discussed the sh stuff at the BR developer meeting and it would be nice if
we had:

- a config option in the system menu that lets the user select the shell: none,
busybox, dash, bash, zsh (default busybox);

- the config option selects the appropriate package;

- target-finalize creates the symlink;

- if sh is busybox, then it's up to the user to choose the appropriate
FEATURE_SH_IS_* option in busybox; we will still create the symlink to busybox
from buildroot.


 Will you take this up? Thanks!


 Regards,
 Arnout


[snip]


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
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

  reply	other threads:[~2014-10-11 14:28 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
2014-10-11 14:28             ` Arnout Vandecappelle [this message]
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=54393E75.2090206@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