From: Frank Lichtenheld <frank@lichtenheld.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] gitweb: Use list form of 'open "-|"' pipeline
Date: Tue, 11 Mar 2008 10:01:00 +0100 [thread overview]
Message-ID: <20080311090100.GN10103@mail-vs.djpig.de> (raw)
In-Reply-To: <20080308165245.15343.62914.stgit@localhost.localdomain>
On Sat, Mar 08, 2008 at 05:57:20PM +0100, Jakub Narebski wrote:
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index a5df2fe..ba97a7b 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -1455,6 +1455,35 @@ sub git_cmd_str {
> return join(' ', git_cmd());
> }
>
> +# my $fh = output_pipeline(['cmd_1', 'option'], ['cmd_2', 'argument']);
> +# is equivalent to (is the "list form" of) the following
> +# open my $fh, "-|", "cmd_1 option | cmd_2 argument"
> +#
> +# Based on http://www.perlmonks.org/?node_id=246397
It might be worthwile to look into how e.g. IPC::Run does this.
> +sub output_pipeline {
> + my @commands_list = @_;
> + exit unless @commands_list;
> +
> + my $pid = open(my $fh, "-|");
> + #die "Couldn't fork: $!" unless defined $pid;
Why are all the die's commented out?
> + if ($pid) { # parent
> + return $fh;
> + }
> +
> + # child
> + COMMAND:
> + while (my $command = pop @commands_list) {
> + my $pid = @commands_list ? open(STDIN, "-|") : -1;
> + #die "Couldn't fork: $!" unless defined $pid;
> +
> + next COMMAND unless ($pid); # parent
> + exec @$command; # child
The "parent" and "child" comments here are wrong, which was really
really confusing...
This should probably be "new child" instead of "parent" and
"old child" instead of "child".
Thw whole concept of processing the array backwards might be shorter,
I personally find it somewhat confusing though.
What happens to all these child processes anyway if one of them fails to
exec?
> + #die "Couldn't exec \"@$command\": $!";
> + }
> +}
> +
> # get HEAD ref of given project as hash
> sub git_get_head_hash {
> my $project = shift;
> @@ -4545,27 +4574,26 @@ sub git_snapshot {
> $hash = git_get_head_hash($project);
> }
>
> - my $git_command = git_cmd_str();
> my $name = $project;
> - $name =~ s,([^/])/*\.git$,$1,;
> + $name =~ s,([^/])/*\.git$,$1,; # strip '.git' or '/.git'
> $name = basename($name);
> - my $filename = to_utf8($name);
> - $name =~ s/\047/\047\\\047\047/g;
> - my $cmd;
> - $filename .= "-$hash$known_snapshot_formats{$format}{'suffix'}";
> - $cmd = "$git_command archive " .
> - "--format=$known_snapshot_formats{$format}{'format'} " .
> - "--prefix=\'$name\'/ $hash";
> + $name = to_utf8($name); # or only for filename, not prefix?
> + $name .= "-$hash";
> +
> + my @cmds = ([git_cmd(), "archive",
> + "--format=$known_snapshot_formats{$format}{'format'}",
> + "--prefix=$name/", $hash]);
> if (exists $known_snapshot_formats{$format}{'compressor'}) {
> - $cmd .= ' | ' . join ' ', @{$known_snapshot_formats{$format}{'compressor'}};
> + push @cmds, $known_snapshot_formats{$format}{'compressor'};
> }
>
> print $cgi->header(
> -type => $known_snapshot_formats{$format}{'type'},
> - -content_disposition => 'inline; filename="' . "$filename" . '"',
> + -content_disposition => 'inline; filename="' .
> + "$filename$known_snapshot_formats{$format}{'suffix'}" . '"',
Huh, that compiles? Where is $filename defined now at all?
> -status => '200 OK');
>
> - open my $fd, "-|", $cmd
> + my $fd = output_pipeline(@cmds)
> or die_error(undef, "Execute git-archive failed");
> binmode STDOUT, ':raw';
> print <$fd>;
Gruesse,
--
Frank Lichtenheld <frank@lichtenheld.de>
www: http://www.djpig.de/
next prev parent reply other threads:[~2008-03-11 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 16:57 [RFC/PATCH] gitweb: Use list form of 'open "-|"' pipeline Jakub Narebski
2008-03-08 17:51 ` Charles Bailey
2008-03-08 18:29 ` Jakub Narebski
2008-03-11 9:01 ` Frank Lichtenheld [this message]
2008-03-11 17:30 ` Jakub Narebski
2008-03-11 18:59 ` Frank Lichtenheld
2008-03-12 2:09 ` Jay Soffian
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=20080311090100.GN10103@mail-vs.djpig.de \
--to=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).