dwarves.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Heckenbach <f.heckenbach@fh-soft.de>
To: bluca@debian.org, acme@kernel.org
Cc: dwarves@vger.kernel.org
Subject: Re: pahole: Problems with lib/include/bpf symlink in a tarball with --transform
Date: Fri, 13 Aug 2021 20:15:16 +0200	[thread overview]
Message-ID: <E1mEbi8-0006Av-1P@mars> (raw)
In-Reply-To: <YRVv1iAX48euE5MO@kernel.org>

Hi,

> The problem is described in this old Debian ticket:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775247
> 
> I'm now trying to figure out what Frank meant when referring to that
> "S" flag.
> 
> I have to figure out what is this 'S' flag (local symlinks, etc) or stop
> using this --transform mechanism to have the dwarves-${version} top
> level directory added when generating the tarball :-\

FWIW, the "S" flag means:

  Do not apply transformation to symbolic link targets.

(see https://www.gnu.org/software/tar/manual/html_node/transform.html
-- it's a bit hard to find in the docs ...)

In my use case, this allows me to build a dist archive from my main
source directory, adding a directory level in the tar, while leaving
symlinks unchanged:

  --transform='s|^|$(DIST_NAME)/|S'

This is not a fully general solution to the problem as I described,
and it may or may not help for your use case.

Viele Grüße,
Frank

      parent reply	other threads:[~2021-08-13 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 19:00 pahole: Problems with lib/include/bpf symlink in a tarball with --transform Arnaldo Carvalho de Melo
2021-08-12 19:06 ` Arnaldo Carvalho de Melo
2021-08-12 21:50   ` Luca Boccassi
2021-08-13  0:05     ` Arnaldo Carvalho de Melo
2021-08-13 18:15 ` Frank Heckenbach [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=E1mEbi8-0006Av-1P@mars \
    --to=f.heckenbach@fh-soft.de \
    --cc=acme@kernel.org \
    --cc=bluca@debian.org \
    --cc=dwarves@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).