Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] bash: add alternative configuration for bin/sh -> /bin/bash
Date: Fri, 27 Mar 2009 23:51:53 +0100	[thread overview]
Message-ID: <gqjla9$k9u$1@ger.gmane.org> (raw)
In-Reply-To: <b6ebd0a50903271402r632461b0q962666a6b2ccd50c@mail.gmail.com>

On 27-03-09 22:02, Chris Larson wrote:
> Be very careful with this.  Specifically, be sure to thoroughly test
> installing bash onto a system that currently has busybox, and the
> upgrade paths for both busybox and bash.  You never want to get into a
> state, due to pre/post rm/install script execution order, where
> /bin/sh doesn't exist.  If that happens, you won't be able to execute
> the next script to fix it :)

And we actually have busyboxisms in some scripts, you can't launch e-wm 
due to the OE wrapper script (which isn't needed anymore, btw) breaking 
with bash.

regards,

Koen


>
> On Fri, Mar 27, 2009 at 1:50 PM, Tim Harvey<tharvey@irobot.com>  wrote:
>> Add alternative configuration for /bin/sh ->  /bin/bash so that for example
>> bash can exist (and override) as shell if busybox is also installed
>>
>> diff --git a/recipes/bash/bash.inc b/recipes/bash/bash.inc
>> index 4eba689..7c6122b 100644
>> --- a/recipes/bash/bash.inc
>> +++ b/recipes/bash/bash.inc
>> @@ -4,7 +4,7 @@ DEPENDS = "ncurses"
>> SECTION = "base/shell"
>> LICENSE = "GPL"
>>
>> -inherit autotools gettext
>> +inherit autotools gettext update-alternatives
>>
>> PARALLEL_MAKE = ""
>>
>> @@ -33,3 +33,8 @@ pkg_postinst () {
>>        grep -q "bin/bash" $D${sysconfdir}/shells || echo /bin/bash>>
>> $D${sysconfdir}/shells
>>        grep -q "bin/sh" $D${sysconfdir}/shells || echo /bin/sh>>
>> $D${sysconfdir}/shells
>> }
>> +
>> +ALTERNATIVE_NAME = "sh"
>> +ALTERNATIVE_LINK = "${base_bindir}/sh"
>> +ALTERNATIVE_PATH = "${base_bindir}/bash"
>> +ALTERNATIVE_PRIORITY = "90"
>> diff --git a/recipes/bash/bash_3.0.bb b/recipes/bash/bash_3.0.bb
>> index e23887a..8165d07 100644
>> --- a/recipes/bash/bash_3.0.bb
>> +++ b/recipes/bash/bash_3.0.bb
>> @@ -1,5 +1,5 @@
>> require bash.inc
>> -PR = "r11"
>> +PR = "r12"
>>
>> SRC_URI += "\
>>   file://bash-3.0-fixes.patch;patch=1 \
>> diff --git a/recipes/bash/bash_3.2.bb b/recipes/bash/bash_3.2.bb
>> index 6a48a4b..e175467 100644
>> --- a/recipes/bash/bash_3.2.bb
>> +++ b/recipes/bash/bash_3.2.bb
>> @@ -1,6 +1,6 @@
>> require bash.inc
>>
>> -PR = "r7"
>> +PR = "r8"
>>
>> SRC_URI += "\
>>            file://builtins.patch;patch=1 \
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
>
>





  reply	other threads:[~2009-03-27 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 20:50 [PATCH] bash: add alternative configuration for bin/sh -> /bin/bash Tim Harvey
2009-03-27 21:02 ` Chris Larson
2009-03-27 22:51   ` Koen Kooi [this message]
2009-04-01 16:26   ` Tim Harvey
2009-04-01 16:52     ` Chris Larson
2009-04-01 17:01       ` Koen Kooi
2009-04-01 17:12         ` Chris Larson

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='gqjla9$k9u$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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