From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Ross Burton <ross@burtonini.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH] meta: use ln -rs instead of lnr
Date: Wed, 10 Nov 2021 21:06:47 +0000 [thread overview]
Message-ID: <e04e01a9a97a4479a1b65c42fe9f464b@axis.com> (raw)
In-Reply-To: <20211110111234.2187460-1-ross.burton@arm.com>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Ross Burton
> Sent: den 10 november 2021 12:13
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] meta: use ln -rs instead of lnr
>
> lnr is a script in oe-core that creates relative symlinks, with the same
> behaviour as `ln --relative --symlink`. It was added back in 2014[1] as
> not all of the supported host distributions at the time shipped
> coreutils 8.16, the first release with --relative.
>
> However the oldest coreutils release in the supported distributions is
> now 8.22 in CentOS 7, so lnr can be deprecated and users switched to ln.
>
> [1] 6ae3b85eaffd1b0b6914422e8de7c1230723157d
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
> meta/classes/image.bbclass | 10 +++++-----
> meta/classes/populate_sdk_ext.bbclass | 4 ++--
> meta/recipes-core/glibc/glibc-package.inc | 4 ++--
> .../images/build-appliance-image_15.0.0.bb | 2 +-
> meta/recipes-core/musl/gcompat_git.bb | 2 +-
> meta/recipes-core/musl/musl_git.bb | 2 +-
> meta/recipes-core/ncurses/ncurses.inc | 4 ++--
> meta/recipes-core/os-release/os-release.bb | 2 +-
> meta/recipes-devtools/dnf/dnf_4.10.0.bb | 4 ++--
> meta/recipes-devtools/pkgconf/pkgconf_1.8.0.bb | 2 +-
> meta/recipes-devtools/pkgconfig/pkgconfig_git.bb | 2 +-
> meta/recipes-kernel/kmod/kmod_git.bb | 4 ++--
> meta/recipes-kernel/linux/kernel-devsrc.bb | 2 +-
> 13 files changed, 22 insertions(+), 22 deletions(-)
>
[cut]
> diff --git a/meta/recipes-core/ncurses/ncurses.inc b/meta/recipes-core/ncurses/ncurses.inc
> index 64cce329aa..3f04545465 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -242,10 +242,10 @@ do_install() {
> mv ${D}${libdir}/libtinfo.so.* ${D}${base_libdir}
> rm ${D}${libdir}/libtinfo.so
>
> - # Use lnr to ensure this is a relative link despite absolute paths
> + # Use ln -rs to ensure this is a relative link despite absolute paths
> # (as we can't know the relationship between base_libdir and libdir).
> # At some point we can rely on coreutils 8.16 which has ln -r.
The last line of the comment can be removed.
> - lnr ${D}${base_libdir}/libtinfo.so.5 ${D}${libdir}/libtinfo.so
> + ln -rs ${D}${base_libdir}/libtinfo.so.5 ${D}${libdir}/libtinfo.so
> fi
> if [ -d "${D}${includedir}/ncurses" ]; then
> for f in `find ${D}${includedir}/ncurses -name "*.h"`
[cut]
//Peter
next prev parent reply other threads:[~2021-11-10 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 11:12 [PATCH] meta: use ln -rs instead of lnr Ross Burton
2021-11-10 21:06 ` Peter Kjellerstedt [this message]
2021-11-10 21:10 ` [OE-core] " Andre McCurdy
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=e04e01a9a97a4479a1b65c42fe9f464b@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.com \
/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