Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base-files/profile: change EDITOR to not be busybox specific
Date: Tue, 10 Feb 2015 19:55:30 -0500	[thread overview]
Message-ID: <20150211005530.GA3150@windriver.com> (raw)
In-Reply-To: <1421864706-26101-1-git-send-email-paul.gortmaker@windriver.com>

[[PATCH] base-files/profile: change EDITOR to not be busybox specific] On 21/01/2015 (Wed 13:25) Paul Gortmaker wrote:

> Setting "EDITOR=/bin/vi" breaks on non-busybox systems, as
> vim will populate /usr/bin/vi instead, and you get stuff like:
> 
>   op3:~/poky/meta-builder$ git commit -s
>   error: cannot run /bin/vi: No such file or directory
>   error: unable to start editor '/bin/vi'

Ping - this seems like the right thing to do, even if we decide to make
busybox LSB compliant at a later date; there is no need to do a full
pathspec for vi.

P.
--

>   Please supply the message using either -m or -F option.
>   op3:~/poky/meta-builder$ which vi
>   /usr/bin/vi
>   op3:~/poky/meta-builder$
> 
> Since we've already specified a proper path above in the profile,
> we've no need to call out where in the path vi lives, and hence
> this will work with busybox and a full vim install w/o busybox.
> 
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
>  meta/recipes-core/base-files/base-files/profile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-core/base-files/base-files/profile b/meta/recipes-core/base-files/base-files/profile
> index 88ab8d877b0d..53c2680409dd 100644
> --- a/meta/recipes-core/base-files/base-files/profile
> +++ b/meta/recipes-core/base-files/base-files/profile
> @@ -2,7 +2,7 @@
>  # and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
>  
>  PATH="/usr/local/bin:/usr/bin:/bin"
> -EDITOR="/bin/vi"			# needed for packages like cron
> +EDITOR="vi"			# needed for packages like cron, git-commit
>  test -z "$TERM" && TERM="vt100"	# Basic terminal capab. For screen etc.
>  
>  if [ ! -e /etc/localtime -a ! -e /etc/TZ ]; then
> -- 
> 2.2.1
> 


      parent reply	other threads:[~2015-02-11  0:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 18:25 [PATCH] base-files/profile: change EDITOR to not be busybox specific Paul Gortmaker
2015-01-21 19:29 ` Dan McGregor
2015-01-22 14:08   ` Mike Looijmans
2015-02-16  0:30   ` Bernhard Reutner-Fischer
2015-02-11  0:55 ` Paul Gortmaker [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=20150211005530.GA3150@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=openembedded-core@lists.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