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:17:40 +0200 [thread overview]
Message-ID: <20180723151740.145c41ea@windsurf> (raw)
In-Reply-To: <1840086717.4674313.1532086956701.JavaMail.zimbra@datacom.com.br>
Hello,
On Fri, 20 Jul 2018 08:42:36 -0300 (BRT), Carlos Santos wrote:
> > But if we allow dangling non-relative symlinks I don't think we want to
> > add this complexity to the vim package, or any other package that
> > installs similar relative symlinks.
>
> The complexity is a consequence of the BR2_ROOTFS_MERGED_USR stuff.
> We already need to deal with such situations in six packages. I'd
> rather declare merged /usr as mandatory and send all those ifeq's
> down the tubes.
Perhaps we could introduce one or two helper functions that hide what
BR2_ROOTFS_MERGED_USR is doing. I thought a few minutes about this and
couldn't find immediately a good semantic/naming, but perhaps this is
a direction that could be investigated ?
Best regards,
Thomas Petazzoni
--
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:17 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 [this message]
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=20180723151740.145c41ea@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.