From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/download: Fix tarball generation - 2020.02.x branch patch
Date: Wed, 24 Mar 2021 12:03:35 +0100 [thread overview]
Message-ID: <87sg4kn794.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210318073240.404490-1-jpcartal@free.fr> (Jean-pierre Cartal's message of "Thu, 18 Mar 2021 08:32:40 +0100")
>>>>> "Jean-pierre" == Jean-pierre Cartal <jpcartal@free.fr> writes:
> fix tarball generation with symlinks pointing to ./something
> When a --transform expression is provided, it is by default also applied
> to the target of a symlink.
> When we create tarballs (from git or svn checkouts), we use a --transform
> expression to replace the leading ./ with the package name and version.
> This causes issues when a package contains symlinks that points to
> ./something, as the leading './' is also replaced.
> Fix that by using the 'S' transformation scope flag, as described in the
> tar manual:
> https://www.gnu.org/software/tar/manual/html_node/transform.html#transform
> In addition, several transformation scope flags are supported, that
> control to what files transformations apply. These are:
> ?r? Apply transformation to regular archive members.
> ?R? Do not apply transformation to regular archive members.
> ?s? Apply transformation to symbolic link targets.
> ?S? Do not apply transformation to symbolic link targets.
> ?h? Apply transformation to hard link targets.
> ?H? Do not apply transformation to hard link targets.
> Default is ?rsh? [...].
> Fixes: #13616
> Signed-off-by: Jean-pierre Cartal <jpcartal@free.fr>
Committed to 2020.02.x and 2020.11.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2021-03-24 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 7:32 [Buildroot] [PATCH 1/1] support/download: Fix tarball generation - 2020.02.x branch patch Jean-pierre Cartal
2021-03-20 17:51 ` Yann E. MORIN
2021-03-24 11:03 ` Peter Korsgaard [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=87sg4kn794.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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