From: <stefan.naewe@atlas-elektronik.com>
To: <rmy@frippery.org>, <git@vger.kernel.org>
Subject: AW: git-archive: --add-virtual-file doesn't seem to respect --prefix
Date: Thu, 15 Feb 2024 11:48:12 +0000 [thread overview]
Message-ID: <a143e25a70b44b82b4ee6fa3bb2bcda4@atlas-elektronik.com> (raw)
In-Reply-To: <65cdaa23.MHIIVADqwryAD0ON%rmy@frippery.org>
Classification - ISMS: Offen | VS: OFFEN
> -----Ursprüngliche Nachricht-----
> Von: Ron Yorston <rmy@frippery.org>
> Gesendet: Donnerstag, 15. Februar 2024 07:08
> An: git@vger.kernel.org
> Betreff: Bug: git-archive: --add-virtual-file doesn't seem to respect --prefix
>
> The man page for git-archive has similar language regarding the --add-file and --
> add-virtual-file options:
>
> The path of the file in the archive is built by concatenating the
> value of the last --prefix option (if any) before...
>
> However this doesn't seem to be true for --add-virtual-file. In any git repository:
>
> $ touch real_added_file
> $ git archive --format=tar --prefix=prefix/ --add-file=real_added_file \
> --add-virtual-file=virtual_added_file: HEAD | \
> tar tvf - | grep added_file
> -rw-rw-r-- root/root 0 2017-02-22 17:18 prefix/real_added_file
> -rw-rw-r-- root/root 0 2017-02-22 17:18 virtual_added_file
>
> I expected to see 'prefix/virtual_added_file'.
>
> Ron
Maybe something like this does the job:
diff --git a/archive.c b/archive.c
index 941495f5d7..b6b885a632 100644
--- a/archive.c
+++ b/archive.c
@@ -331,11 +331,11 @@ int write_archive_entries(struct archiver_args *args,
put_be64(fake_oid.hash, i + 1);
+ strbuf_reset(&path_in_archive);
+ if (info->base)
+ strbuf_addstr(&path_in_archive, info->base);
+ strbuf_addstr(&path_in_archive, basename(path));
if (!info->content) {
- strbuf_reset(&path_in_archive);
- if (info->base)
- strbuf_addstr(&path_in_archive, info->base);
- strbuf_addstr(&path_in_archive, basename(path));
strbuf_reset(&content);
if (strbuf_read_file(&content, path, info->stat.st_size) < 0)
@@ -347,7 +347,7 @@ int write_archive_entries(struct archiver_args *args,
content.buf, content.len);
} else {
err = write_entry(args, &fake_oid,
- path, strlen(path),
+ path_in_archive.buf, path_in_archive.len,
canon_mode(info->stat.st_mode),
info->content, info->stat.st_size);
}
Stefan
prev parent reply other threads:[~2024-02-15 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 6:07 Bug: git-archive: --add-virtual-file doesn't seem to respect --prefix Ron Yorston
2024-02-15 11:48 ` stefan.naewe [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=a143e25a70b44b82b4ee6fa3bb2bcda4@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik.com \
--cc=git@vger.kernel.org \
--cc=rmy@frippery.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).