From: Jeff King <peff@peff.net>
To: Neal Kreitzinger <neal@rsss.com>
Cc: git@vger.kernel.org
Subject: Re: git-archive and tar options
Date: Wed, 13 Jul 2011 21:56:56 -0400 [thread overview]
Message-ID: <20110714015656.GA20136@sigill.intra.peff.net> (raw)
In-Reply-To: <ivla29$liu$1@dough.gmane.org>
On Wed, Jul 13, 2011 at 06:34:32PM -0500, Neal Kreitzinger wrote:
> the git-archive manpage states:
>
> "git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>] [-o
> | --output=<file>] [--worktree-attributes] [--remote=<repo>
> [--exec=<git-upload-archive>]] <tree-ish> [path\u2026]
>
> <extra>
> This can be any options that the archiver backend understands. See next
> section."
>
> I have tar 1.23 and want to use the --transform option. How can I feed
> git-archive additional tar options?
Right. And the next section is "Backend Extra Options", which has:
zip
-0
Store the files instead of deflating them.
-9
Highest and slowest compression level. You can specify any number from 1 to 9
to adjust compression speed and ratio.
And nothing else. We don't actually call your system "tar" to generate
the tarball, which is what I assume you thought when you saw "backend".
A patch to make it more clear would be welcome.
> Working syntax starting points for git-archive and tar:
>
> git archive --format=tar -o my.tar HEAD Web/Templates/
> tar -cvf my.tar --transform 's,^Web/Templates/,myPath/myWeb/Templates/,'
> WebPortal/Templates/
>
> Failed syntax attempts for feeding tar option to git-archive:
>
> git archive --format=tar -o my.tar HEAD --transform
> 's,^Web/Templates/,myPath/myWeb/Templates/,' WebPortal/Templates/
> error: unknown option `transform'
>
> git archive --format=tar -o my.tar --transform
> 's,^Web/Templates/,myPath/myWeb/Templates/,' HEAD WebPortal/Templates/
> error: unknown option `transform'
Yeah, that won't work, because there is no such option. We do have
"--prefix", but I suspect that's not flexible enough for what you want.
So you're probably stuck with extracting the results of "git archive" to
a temporary directory and then using GNU tar to re-archive them (or if
you have a checkout, you can just tar that up directly, feeding the list
from "git ls-files" into tar). It would be nice if GNU tar could act as
a post-processor, and do something like:
git archive HEAD | tar --pipe-mode --transform=whatever >my.tar
But AFAIK, nothing like "--pipe-mode" exists.
It would probably not be a very hard feature to add to "git archive" if
you're interested in doing so.
-Peff
next prev parent reply other threads:[~2011-07-14 1:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 23:34 git-archive and tar options Neal Kreitzinger
2011-07-14 1:56 ` Jeff King [this message]
2011-07-14 17:16 ` René Scharfe
2011-07-14 17:27 ` Jeff King
2011-07-14 17:45 ` René Scharfe
2011-07-14 18:18 ` Jeff King
2011-07-14 19:12 ` Jakub Narebski
2011-07-14 21:23 ` Junio C Hamano
2011-07-14 21:25 ` Jeff King
2011-07-14 23:30 ` Junio C Hamano
2011-07-15 20:59 ` René Scharfe
2011-07-18 19:31 ` Neal Kreitzinger
2011-07-18 20:50 ` René Scharfe
2011-07-14 21:38 ` Jakub Narebski
2011-07-18 18:13 ` Neal Kreitzinger
2011-07-18 20:50 ` René Scharfe
2011-07-19 0:12 ` Neal Kreitzinger
2011-07-19 17:56 ` René Scharfe
2011-07-21 2:13 ` Neal Kreitzinger
2011-07-21 16:59 ` Neal Kreitzinger
2011-07-14 17:48 ` Andreas Schwab
2011-07-19 20:10 ` Sylvain Rabot
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=20110714015656.GA20136@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=neal@rsss.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;
as well as URLs for NNTP newsgroup(s).