From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] vim: install /bin/vi as a relative symlink
Date: Mon, 23 Jul 2018 15:08:15 +0200 [thread overview]
Message-ID: <20180723150815.304d1c9d@windsurf> (raw)
In-Reply-To: <87fu0g53wd.fsf@tkos.co.il>
Hello,
On Thu, 19 Jul 2018 05:57:06 +0300, Baruch Siach wrote:
> My vim patch is at
>
> http://patchwork.ozlabs.org/patch/943314/
>
> I marked it as Rejected following the comment of Arnout. Carlos' patch
> works around the merged /usr issue by changing the symlink target for
> merged /usr. In my opinion this solution is error prone. It would be
> much easier to allow dangling symlinks in the target directory, and
> tweak the busybox install.sh to cope with that. That's what my pending
> busybox patch suggests.
>
> http://patchwork.ozlabs.org/patch/944884/
Allowing dangling symlinks is indeed desirable, but I think it is also
nice if we have as few dangling symlinks are possible. It looks cleaner
to me. So like Carlos said, I believe both your patch fixing the
Busybox installation and Carlos patch adjusting vim are useful.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-23 13:08 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 [this message]
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=20180723150815.304d1c9d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.