From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>,
openembedded-core@lists.openembedded.org
Cc: haris.okanovic@ni.com, ken.sharp@ni.com
Subject: Re: [PATCH] oe/path.py: copyhardlinktree: don't overwrite existing symlinks
Date: Fri, 18 Aug 2017 10:53:37 +0100 [thread overview]
Message-ID: <1503050017.32591.7.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170816111355.11347-1-adrian.ratiu@ni.com>
On Wed, 2017-08-16 at 14:13 +0300, Ioan-Adrian Ratiu wrote:
> Starting with tar>=1.26 the default behaviour when extracting is to
> overwrite symlinks and a '-h' flag was added for tar to follow them.
>
> The primary use case for this is to allow ${DEPLOY_DIR_IPK/RPM/DEB}
> to
> be symlinks and avoid copyhardlinktree replacing those symlinks with
> a
> normal directory.
>
> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
> ---
> meta/lib/oe/path.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Does the -h option exist for tar < 1.26?
Cheers,
Richard
next prev parent reply other threads:[~2017-08-18 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 11:13 [PATCH] oe/path.py: copyhardlinktree: don't overwrite existing symlinks Ioan-Adrian Ratiu
2017-08-18 9:53 ` Richard Purdie [this message]
2017-08-21 10:45 ` Ioan-Adrian Ratiu
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=1503050017.32591.7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=adrian.ratiu@ni.com \
--cc=haris.okanovic@ni.com \
--cc=ken.sharp@ni.com \
--cc=openembedded-core@lists.openembedded.org \
/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