Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] vim: install /bin/vi as a relative symlink
Date: Sun, 5 Aug 2018 14:43:03 +0200	[thread overview]
Message-ID: <20180805144303.7624b65a@windsurf> (raw)
In-Reply-To: <20180718123443.7242-1-casantos@datacom.com.br>

Hello,

On Wed, 18 Jul 2018 09:34:43 -0300, Carlos Santos wrote:
> Prevent creating a dangling symlink when vim is not present on the host
> machine. With BR2_ROOTFS_MERGED_USR, just link to "vim", since they are
> on the same directory, otherwise link to "../usr/bin/vim".
> 
> Signed-off-by: Carlos Santos <casantos@datacom.com.br>
> ---
>  package/vim/vim.mk | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)

I know there is some ongoing discussion on how to handle this better in
a more generic way, but until those discussions are resolved, I've
applied this patch to master.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-08-05 12:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 12:34 [Buildroot] [PATCH] vim: install /bin/vi as a relative symlink Carlos Santos
2018-07-18 13:03 ` Thomas Petazzoni
2018-07-18 14:10   ` Carlos Santos
2018-07-19  2:57   ` Baruch Siach
2018-07-19 10:58     ` Carlos Santos
2018-07-20  5:58       ` Baruch Siach
2018-07-20 11:42         ` Carlos Santos
2018-07-23 13:17           ` Thomas Petazzoni
2018-07-24  7:55             ` Arnout Vandecappelle
2018-07-24  8:30               ` Thomas Petazzoni
2018-07-26  8:39                 ` Arnout Vandecappelle
2018-07-23 13:08     ` Thomas Petazzoni
2018-08-05 12:43 ` Thomas Petazzoni [this message]
2018-08-23 22:09   ` 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=20180805144303.7624b65a@windsurf \
    --to=thomas.petazzoni@bootlin.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