From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] vim: install /bin/vi as a relative symlink
Date: Tue, 24 Jul 2018 10:30:31 +0200 [thread overview]
Message-ID: <20180724103031.1b1cd416@windsurf> (raw)
In-Reply-To: <93989b29-232f-20a2-4ac4-835066e5229b@mind.be>
Hello,
On Tue, 24 Jul 2018 09:55:40 +0200, Arnout Vandecappelle wrote:
> The thing is, I don't believe that relying on BR2_ROOTFS_MERGED_USR is the
> right approach. I've had projects with a usr -> . symlink in a custom skeleton,
> for instance. We could of course declare such a skeleton invalid, but I don't
> think that it is checked currently. Also I can imagine that there could be other
> custom skeleton layouts that could create problems.
>
> We already use ln --relative in a few places, isn't that the easiest solution?
ln --relative is not supported on old distros, we even have a patch on
systemd to remove its use of ln --relative.
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-24 8:30 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 [this message]
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=20180724103031.1b1cd416@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.