All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [RFC] system: add option to choose what /bin/sh points to
Date: Sun, 12 Oct 2014 15:46:01 +0200	[thread overview]
Message-ID: <87siitxuxy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <543A7EF9.2080106@mind.be> (Arnout Vandecappelle's message of "Sun, 12 Oct 2014 15:15:37 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

 >> But we default to BR2_INIT_BUSYBOX, so you still need to go into the
 >> system menu and disable that before you can deselect busybox.
 >> 
 >> Another issue with the 'depends on' is that if you disable busybox the
 >> choice then jumps to the next option which pulls in bash (which might
 >> not really be what you want when you try to save space by disabling
 >> busybox).
 >> 
 >> So I think it is better to use selects everywhere.

 >  I disagree.

 >  For people who want to avoid busybox, it is already annoying that they have to
 > change their init system first. Adding more implicit selects of busybox is not
 > going to make their life easier.

 >  For the jumping, it's better to fix it by adding a 'default dash if !busybox' line.

 >  And since busybox is on by default, there is no strong need for a select - if
 > the user deselects busybox I guess they know what they're doing.

 >  And also using a depends solves the issue you mention below :-)

Ok, that's also fine by me.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-10-12 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-11 17:49 [Buildroot] [PATCH] [RFC] system: add option to choose what /bin/sh points to Yann E. MORIN
2014-10-12  9:57 ` Peter Korsgaard
2014-10-12 13:15   ` Arnout Vandecappelle
2014-10-12 13:46     ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-12 13:36 Yann E. MORIN
2014-10-12 13:51 ` 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=87siitxuxy.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.