From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] vim: install /bin/vi as a relative symlink
Date: Wed, 18 Jul 2018 09:34:43 -0300 [thread overview]
Message-ID: <20180718123443.7242-1-casantos@datacom.com.br> (raw)
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(-)
diff --git a/package/vim/vim.mk b/package/vim/vim.mk
index dbf71c573f..ee0c8b61e4 100644
--- a/package/vim/vim.mk
+++ b/package/vim/vim.mk
@@ -63,9 +63,15 @@ define VIM_REMOVE_DOCS
endef
# Avoid oopses with vipw/vigr, lack of $EDITOR and 'vi' command expectation
+ifeq ($(BR2_ROOTFS_MERGED_USR),y)
define VIM_INSTALL_VI_SYMLINK
- ln -sf /usr/bin/vim $(TARGET_DIR)/bin/vi
+ ln -sf vim $(TARGET_DIR)/usr/bin/vi
endef
+else
+define VIM_INSTALL_VI_SYMLINK
+ ln -sf ../usr/bin/vim $(TARGET_DIR)/bin/vi
+endef
+endif
VIM_POST_INSTALL_TARGET_HOOKS += VIM_INSTALL_VI_SYMLINK
ifeq ($(BR2_PACKAGE_VIM_RUNTIME),y)
--
2.14.4
next reply other threads:[~2018-07-18 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 12:34 Carlos Santos [this message]
2018-07-18 13:03 ` [Buildroot] [PATCH] vim: install /bin/vi as a relative symlink 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
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=20180718123443.7242-1-casantos@datacom.com.br \
--to=casantos@datacom.com.br \
--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