Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: enable fully featured hush shell for nommu
Date: Fri, 16 Oct 2015 11:55:34 +0200	[thread overview]
Message-ID: <87twpr2l49.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <561FD606.2080905@mind.be> (Arnout Vandecappelle's message of "Thu, 15 Oct 2015 18:36:22 +0200")

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

Hi,

 >> +	$(call KCONFIG_ENABLE_OPT,CONFIG_HUSH_LOCAL,$(BUSYBOX_BUILD_CONFIG))
 >> +	$(call KCONFIG_ENABLE_OPT,CONFIG_HUSH_RANDOM_SUPPORT,$(BUSYBOX_BUILD_CONFIG))
 >> +	$(call KCONFIG_ENABLE_OPT,CONFIG_HUSH_EXPORT_N,$(BUSYBOX_BUILD_CONFIG))
 >> +	$(call KCONFIG_ENABLE_OPT,CONFIG_HUSH_MODE_X,$(BUSYBOX_BUILD_CONFIG))

 >  I don't like this, since it makes it completely impossible to disable these
 > hush features. I admit that it indeed doesn't make a significant difference, but
 > on principle I'm against forcing this on the user.

Yeah, I also don't think this is really nice.

 >  But then we're running the fixups three times in the configure step, which
 > feels a bit like overkill to me. So perhaps a more elegant solution would be the
 > following: instead of calling sed-based fixups, use a kconfig fragment and
 > merge_config to apply the fixups.

 >  Cc-ing our Kconfig infra expert to consider this.

Lets here what he has to say ;) A further complication is that busybox
uses a really old kconfig version.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2015-10-16  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 22:36 [Buildroot] [PATCH] busybox: enable fully featured hush shell for nommu Gustavo Zacarias
2015-10-15  7:40 ` Thomas Petazzoni
2015-10-15 16:36 ` Arnout Vandecappelle
2015-10-16  9:55   ` Peter Korsgaard [this message]

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=87twpr2l49.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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