All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] dash: bump to version 0.5.8-1
Date: Wed, 08 Oct 2014 20:46:19 +0200	[thread overview]
Message-ID: <87y4sqbds4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <543580C6.1090600@zacarias.com.ar> (Gustavo Zacarias's message of "Wed, 08 Oct 2014 15:21:58 -0300")

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

Hi,

 > On 10/08/2014 03:05 PM, Peter Korsgaard wrote:
 >> Random is not good, so I suggest we either:
 >> 
 >> - Only do it for bash like today

 > That's not an option: non-usable default rootfs if there's no /bin/sh.

But a buildroot config without busybox is quite unlikely.


 >> - Provide an option for the user to select

 > 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.


 >> - Decide on a fixed priority order (E.G. busybox->dash->zsh->bash) and
 >> tell people to use a post-build script if they are not happy with it

 > It's a pretty arbitrary decision, many people would balk at the idea of
 > having bash as default yet they may need it for other uses.

Sure it is arbitrary, but that's what we have today and I haven't heard
anybody complaining.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-10-08 18:46 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 [this message]
2014-10-08 19:16           ` Gustavo Zacarias
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=87y4sqbds4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.