From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/systemd: better patch to avoid ln --relative
Date: Mon, 3 Apr 2017 22:48:31 +0200 [thread overview]
Message-ID: <20170403224831.26c98ff4@free-electrons.com> (raw)
In-Reply-To: <20170401173813.23665-1-yann.morin.1998@free.fr>
Hello,
On Sat, 1 Apr 2017 19:38:13 +0200, Yann E. MORIN wrote:
> We currently have two patches that address the ln --relative issue
> differently. The first one changes the behaviour to generate absolute
> symlinks, which is incorrect; the second provides an ad-hoc solution
> for a single case.
>
> Replace both of them with a single patch that mimics ln --relative when
> the host ln does not support it.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> ---
> .../systemd/0002-build-check-for-ln-relative.patch | 96 ++++++++++++++++++++++
> ...uild-sys-revert-use-of-ln-relative-option.patch | 72 ----------------
> .../0004-install-don-t-use-ln-relative.patch | 40 ---------
> 3 files changed, 96 insertions(+), 112 deletions(-)
> create mode 100644 package/systemd/0002-build-check-for-ln-relative.patch
> delete mode 100644 package/systemd/0002-build-sys-revert-use-of-ln-relative-option.patch
> delete mode 100644 package/systemd/0004-install-don-t-use-ln-relative.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-04-03 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 17:38 [Buildroot] [PATCH] package/systemd: better patch to avoid ln --relative Yann E. MORIN
2017-04-03 20:48 ` Thomas Petazzoni [this message]
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=20170403224831.26c98ff4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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