3 Git - Perl interface to the Git version control system
15 our ($VERSION, @ISA, @EXPORT, @EXPORT_OK);
17 # Totally unstable API.
25 my $version = Git::command_oneline('version');
27 git_cmd_try { Git::command_noisy('update-server-info') }
28 '%s failed w/ code %d';
30 my $repo = Git->repository (Directory => '/srv/git/cogito.git');
33 my @revs = $repo->command('rev-list', '--since=last monday', '--all');
35 my ($fh, $c) = $repo->command_output_pipe('rev-list', '--since=last monday', '--all');
36 my $lastrev = <$fh>; chomp $lastrev;
37 $repo->command_close_pipe($fh, $c);
39 my $lastrev = $repo->command_oneline( [ 'rev-list', '--all' ],
49 @EXPORT = qw(git_cmd_try);
51 # Methods which can be called as standalone functions as well:
52 @EXPORT_OK = qw(command command_oneline command_noisy
53 command_output_pipe command_input_pipe command_close_pipe
54 version exec_path hash_object git_cmd_try);
59 This module provides Perl scripts easy way to interface the Git version control
60 system. The modules have an easy and well-tested way to call arbitrary Git
61 commands; in the future, the interface will also provide specialized methods
62 for doing easily operations which are not totally trivial to do over
63 the generic command interface.
65 While some commands can be executed outside of any context (e.g. 'version'
66 or 'init'), most operations require a repository context, which in practice
67 means getting an instance of the Git object using the repository() constructor.
68 (In the future, we will also get a new_repository() constructor.) All commands
69 called as methods of the object are then executed in the context of the
72 Part of the "repository state" is also information about path to the attached
73 working copy (unless you work with a bare repository). You can also navigate
74 inside of the working copy using the C<wc_chdir()> method. (Note that
75 the repository object is self-contained and will not change working directory
78 TODO: In the future, we might also do
80 my $remoterepo = $repo->remote_repository (Name => 'cogito', Branch => 'master');
81 $remoterepo ||= Git->remote_repository ('http://git.or.cz/cogito.git/');
82 my @refs = $remoterepo->refs();
84 Currently, the module merely wraps calls to external Git tools. In the future,
85 it will provide a much faster way to interact with Git by linking directly
86 to libgit. This should be completely opaque to the user, though (performance
87 increate nonwithstanding).
92 use Carp
qw(carp croak); # but croak is bad - throw instead
103 =item repository ( OPTIONS )
105 =item repository ( DIRECTORY )
109 Construct a new repository object.
110 C<OPTIONS> are passed in a hash like fashion, using key and value pairs.
111 Possible options are:
113 B<Repository> - Path to the Git repository.
115 B<WorkingCopy> - Path to the associated working copy; not strictly required
116 as many commands will happily crunch on a bare repository.
118 B<WorkingSubdir> - Subdirectory in the working copy to work inside.
119 Just left undefined if you do not want to limit the scope of operations.
121 B<Directory> - Path to the Git working directory in its usual setup.
122 The C<.git> directory is searched in the directory and all the parent
123 directories; if found, C<WorkingCopy> is set to the directory containing
124 it and C<Repository> to the C<.git> directory itself. If no C<.git>
125 directory was found, the C<Directory> is assumed to be a bare repository,
126 C<Repository> is set to point at it and C<WorkingCopy> is left undefined.
127 If the C<$GIT_DIR> environment variable is set, things behave as expected
130 You should not use both C<Directory> and either of C<Repository> and
131 C<WorkingCopy> - the results of that are undefined.
133 Alternatively, a directory path may be passed as a single scalar argument
134 to the constructor; it is equivalent to setting only the C<Directory> option
137 Calling the constructor with no options whatsoever is equivalent to
138 calling it with C<< Directory => '.' >>. In general, if you are building
139 a standard porcelain command, simply doing C<< Git->repository() >> should
140 do the right thing and setup the object to reflect exactly where the user
151 if (defined $args[0]) {
152 if ($#args % 2 != 1) {
154 $#args == 0 or throw Error
::Simple
("bad usage");
155 %opts = ( Directory
=> $args[0] );
161 if (not defined $opts{Repository
} and not defined $opts{WorkingCopy
}) {
162 $opts{Directory
} ||= '.';
165 if ($opts{Directory
}) {
166 -d
$opts{Directory
} or throw Error
::Simple
("Directory not found: $!");
168 my $search = Git
->repository(WorkingCopy
=> $opts{Directory
});
171 $dir = $search->command_oneline(['rev-parse', '--git-dir'],
173 } catch Git
::Error
::Command with
{
178 $dir =~ m
#^/# or $dir = $opts{Directory} . '/' . $dir;
179 $opts{Repository
} = $dir;
181 # If --git-dir went ok, this shouldn't die either.
182 my $prefix = $search->command_oneline('rev-parse', '--show-prefix');
183 $dir = abs_path
($opts{Directory
}) . '/';
185 if (substr($dir, -length($prefix)) ne $prefix) {
186 throw Error
::Simple
("rev-parse confused me - $dir does not have trailing $prefix");
188 substr($dir, -length($prefix)) = '';
190 $opts{WorkingCopy
} = $dir;
191 $opts{WorkingSubdir
} = $prefix;
194 # A bare repository? Let's see...
195 $dir = $opts{Directory
};
197 unless (-d
"$dir/refs" and -d
"$dir/objects" and -e
"$dir/HEAD") {
198 # Mimick git-rev-parse --git-dir error message:
199 throw Error
::Simple
('fatal: Not a git repository');
201 my $search = Git
->repository(Repository
=> $dir);
203 $search->command('symbolic-ref', 'HEAD');
204 } catch Git
::Error
::Command with
{
205 # Mimick git-rev-parse --git-dir error message:
206 throw Error
::Simple
('fatal: Not a git repository');
209 $opts{Repository
} = abs_path
($dir);
212 delete $opts{Directory
};
215 $self = { opts
=> \
%opts };
226 =item command ( COMMAND [, ARGUMENTS... ] )
228 =item command ( [ COMMAND, ARGUMENTS... ], { Opt => Val ... } )
230 Execute the given Git C<COMMAND> (specify it without the 'git-'
231 prefix), optionally with the specified extra C<ARGUMENTS>.
233 The second more elaborate form can be used if you want to further adjust
234 the command execution. Currently, only one option is supported:
236 B<STDERR> - How to deal with the command's error output. By default (C<undef>)
237 it is delivered to the caller's C<STDERR>. A false value (0 or '') will cause
238 it to be thrown away. If you want to process it, you can get it in a filehandle
239 you specify, but you must be extremely careful; if the error output is not
240 very short and you want to read it in the same process as where you called
241 C<command()>, you are set up for a nice deadlock!
243 The method can be called without any instance or on a specified Git repository
244 (in that case the command will be run in the repository context).
246 In scalar context, it returns all the command output in a single string
249 In array context, it returns an array containing lines printed to the
250 command's stdout (without trailing newlines).
252 In both cases, the command's stdin and stderr are the same as the caller's.
257 my ($fh, $ctx) = command_output_pipe
(@_);
259 if (not defined wantarray) {
260 # Nothing to pepper the possible exception with.
261 _cmd_close
($fh, $ctx);
263 } elsif (not wantarray) {
267 _cmd_close
($fh, $ctx);
268 } catch Git
::Error
::Command with
{
269 # Pepper with the output:
271 $E->{'-outputref'} = \
$text;
278 defined and chomp for @lines;
280 _cmd_close
($fh, $ctx);
281 } catch Git
::Error
::Command with
{
283 $E->{'-outputref'} = \
@lines;
291 =item command_oneline ( COMMAND [, ARGUMENTS... ] )
293 =item command_oneline ( [ COMMAND, ARGUMENTS... ], { Opt => Val ... } )
295 Execute the given C<COMMAND> in the same way as command()
296 does but always return a scalar string containing the first line
297 of the command's standard output.
301 sub command_oneline
{
302 my ($fh, $ctx) = command_output_pipe
(@_);
305 defined $line and chomp $line;
307 _cmd_close
($fh, $ctx);
308 } catch Git
::Error
::Command with
{
309 # Pepper with the output:
311 $E->{'-outputref'} = \
$line;
318 =item command_output_pipe ( COMMAND [, ARGUMENTS... ] )
320 =item command_output_pipe ( [ COMMAND, ARGUMENTS... ], { Opt => Val ... } )
322 Execute the given C<COMMAND> in the same way as command()
323 does but return a pipe filehandle from which the command output can be
326 The function can return C<($pipe, $ctx)> in array context.
327 See C<command_close_pipe()> for details.
331 sub command_output_pipe
{
332 _command_common_pipe
('-|', @_);
336 =item command_input_pipe ( COMMAND [, ARGUMENTS... ] )
338 =item command_input_pipe ( [ COMMAND, ARGUMENTS... ], { Opt => Val ... } )
340 Execute the given C<COMMAND> in the same way as command_output_pipe()
341 does but return an input pipe filehandle instead; the command output
344 The function can return C<($pipe, $ctx)> in array context.
345 See C<command_close_pipe()> for details.
349 sub command_input_pipe
{
350 _command_common_pipe
('|-', @_);
354 =item command_close_pipe ( PIPE [, CTX ] )
356 Close the C<PIPE> as returned from C<command_*_pipe()>, checking
357 whether the command finished successfully. The optional C<CTX> argument
358 is required if you want to see the command name in the error message,
359 and it is the second value returned by C<command_*_pipe()> when
360 called in array context. The call idiom is:
362 my ($fh, $ctx) = $r->command_output_pipe('status');
363 while (<$fh>) { ... }
364 $r->command_close_pipe($fh, $ctx);
366 Note that you should not rely on whatever actually is in C<CTX>;
367 currently it is simply the command name but in future the context might
368 have more complicated structure.
372 sub command_close_pipe
{
373 my ($self, $fh, $ctx) = _maybe_self
(@_);
374 $ctx ||= '<unknown>';
375 _cmd_close
($fh, $ctx);
379 =item command_noisy ( COMMAND [, ARGUMENTS... ] )
381 Execute the given C<COMMAND> in the same way as command() does but do not
382 capture the command output - the standard output is not redirected and goes
383 to the standard output of the caller application.
385 While the method is called command_noisy(), you might want to as well use
386 it for the most silent Git commands which you know will never pollute your
387 stdout but you want to avoid the overhead of the pipe setup when calling them.
389 The function returns only after the command has finished running.
394 my ($self, $cmd, @args) = _maybe_self
(@_);
395 _check_valid_cmd
($cmd);
398 if (not defined $pid) {
399 throw Error
::Simple
("fork failed: $!");
400 } elsif ($pid == 0) {
401 _cmd_exec
($self, $cmd, @args);
403 if (waitpid($pid, 0) > 0 and $?
>>8 != 0) {
404 throw Git
::Error
::Command
(join(' ', $cmd, @args), $?
>> 8);
411 Return the Git version in use.
416 my $verstr = command_oneline
('--version');
417 $verstr =~ s/^git version //;
424 Return path to the Git sub-command executables (the same as
425 C<git --exec-path>). Useful mostly only internally.
429 sub exec_path
{ command_oneline
('--exec-path') }
434 Return path to the git repository. Must be called on a repository instance.
438 sub repo_path
{ $_[0]->{opts
}->{Repository
} }
443 Return path to the working copy. Must be called on a repository instance.
447 sub wc_path
{ $_[0]->{opts
}->{WorkingCopy
} }
452 Return path to the subdirectory inside of a working copy. Must be called
453 on a repository instance.
457 sub wc_subdir
{ $_[0]->{opts
}->{WorkingSubdir
} ||= '' }
460 =item wc_chdir ( SUBDIR )
462 Change the working copy subdirectory to work within. The C<SUBDIR> is
463 relative to the working copy root directory (not the current subdirectory).
464 Must be called on a repository instance attached to a working copy
465 and the directory must exist.
470 my ($self, $subdir) = @_;
472 or throw Error
::Simple
("bare repository");
474 -d
$self->wc_path().'/'.$subdir
475 or throw Error
::Simple
("subdir not found: $!");
476 # Of course we will not "hold" the subdirectory so anyone
477 # can delete it now and we will never know. But at least we tried.
479 $self->{opts
}->{WorkingSubdir
} = $subdir;
483 =item config ( VARIABLE )
485 Retrieve the configuration C<VARIABLE> in the same manner as C<config>
486 does. In scalar context requires the variable to be set only one time
487 (exception is thrown otherwise), in array context returns allows the
488 variable to be set multiple times and returns all the values.
490 Must be called on a repository instance.
492 This currently wraps command('config') so it is not so fast.
497 my ($self, $var) = @_;
499 or throw Error
::Simple
("not a repository");
503 return $self->command('config', '--get-all', $var);
505 return $self->command_oneline('config', '--get', $var);
507 } catch Git
::Error
::Command with
{
509 if ($E->value() == 1) {
519 =item config_bool ( VARIABLE )
521 Retrieve the bool configuration C<VARIABLE>. The return value
522 is usable as a boolean in perl (and C<undef> if it's not defined,
525 Must be called on a repository instance.
527 This currently wraps command('config') so it is not so fast.
532 my ($self, $var) = @_;
534 or throw Error
::Simple
("not a repository");
537 my $val = $self->command_oneline('config', '--bool', '--get',
539 return undef unless defined $val;
540 return $val eq 'true';
541 } catch Git
::Error
::Command with
{
543 if ($E->value() == 1) {
553 =item ident ( TYPE | IDENTSTR )
555 =item ident_person ( TYPE | IDENTSTR | IDENTARRAY )
557 This suite of functions retrieves and parses ident information, as stored
558 in the commit and tag objects or produced by C<var GIT_type_IDENT> (thus
559 C<TYPE> can be either I<author> or I<committer>; case is insignificant).
561 The C<ident> method retrieves the ident information from C<git-var>
562 and either returns it as a scalar string or as an array with the fields parsed.
563 Alternatively, it can take a prepared ident string (e.g. from the commit
564 object) and just parse it.
566 C<ident_person> returns the person part of the ident - name and email;
567 it can take the same arguments as C<ident> or the array returned by C<ident>.
569 The synopsis is like:
571 my ($name, $email, $time_tz) = ident('author');
572 "$name <$email>" eq ident_person('author');
573 "$name <$email>" eq ident_person($name);
574 $time_tz =~ /^\d+ [+-]\d{4}$/;
576 Both methods must be called on a repository instance.
581 my ($self, $type) = @_;
583 if (lc $type eq lc 'committer' or lc $type eq lc 'author') {
584 $identstr = $self->command_oneline('var', 'GIT_'.uc($type).'_IDENT');
589 return $identstr =~ /^(.*) <(.*)> (\d+ [+-]\d{4})$/;
596 my ($self, @ident) = @_;
597 $#ident == 0 and @ident = $self->ident($ident[0]);
598 return "$ident[0] <$ident[1]>";
602 =item hash_object ( TYPE, FILENAME )
604 Compute the SHA1 object id of the given C<FILENAME> (or data waiting in
605 C<FILEHANDLE>) considering it is of the C<TYPE> object type (C<blob>,
608 The method can be called without any instance or on a specified Git repository,
609 it makes zero difference.
611 The function returns the SHA1 hash.
615 # TODO: Support for passing FILEHANDLE instead of FILENAME
617 my ($self, $type, $file) = _maybe_self
(@_);
618 command_oneline
('hash-object', '-t', $type, $file);
625 =head1 ERROR HANDLING
627 All functions are supposed to throw Perl exceptions in case of errors.
628 See the L<Error> module on how to catch those. Most exceptions are mere
629 L<Error::Simple> instances.
631 However, the C<command()>, C<command_oneline()> and C<command_noisy()>
632 functions suite can throw C<Git::Error::Command> exceptions as well: those are
633 thrown when the external command returns an error code and contain the error
634 code as well as access to the captured command's output. The exception class
635 provides the usual C<stringify> and C<value> (command's exit code) methods and
636 in addition also a C<cmd_output> method that returns either an array or a
637 string with the captured command output (depending on the original function
638 call context; C<command_noisy()> returns C<undef>) and $<cmdline> which
639 returns the command and its arguments (but without proper quoting).
641 Note that the C<command_*_pipe()> functions cannot throw this exception since
642 it has no idea whether the command failed or not. You will only find out
643 at the time you C<close> the pipe; if you want to have that automated,
644 use C<command_close_pipe()>, which can throw the exception.
649 package Git
::Error
::Command
;
651 @Git::Error
::Command
::ISA
= qw(Error);
655 my $cmdline = '' . shift;
656 my $value = 0 + shift;
657 my $outputref = shift;
660 local $Error::Depth
= $Error::Depth
+ 1;
662 push(@args, '-cmdline', $cmdline);
663 push(@args, '-value', $value);
664 push(@args, '-outputref', $outputref);
666 $self->SUPER::new
(-text
=> 'command returned error', @args);
671 my $text = $self->SUPER::stringify
;
672 $self->cmdline() . ': ' . $text . ': ' . $self->value() . "\n";
682 my $ref = $self->{'-outputref'};
683 defined $ref or undef;
684 if (ref $ref eq 'ARRAY') {
694 =item git_cmd_try { CODE } ERRMSG
696 This magical statement will automatically catch any C<Git::Error::Command>
697 exceptions thrown by C<CODE> and make your program die with C<ERRMSG>
698 on its lips; the message will have %s substituted for the command line
699 and %d for the exit status. This statement is useful mostly for producing
700 more user-friendly error messages.
702 In case of no exception caught the statement returns C<CODE>'s return value.
704 Note that this is the only auto-exported function.
708 sub git_cmd_try
(&$) {
709 my ($code, $errmsg) = @_;
712 my $array = wantarray;
719 } catch Git
::Error
::Command with
{
722 $err =~ s/\%s/$E->cmdline()/ge;
723 $err =~ s/\%d/$E->value()/ge;
724 # We can't croak here since Error.pm would mangle
725 # that to Error::Simple.
728 return $array ?
@result : $result[0];
736 Copyright 2006 by Petr Baudis E<lt>pasky@suse.czE<gt>.
738 This module is free software; it may be used, copied, modified
739 and distributed under the terms of the GNU General Public Licence,
740 either version 2, or (at your option) any later version.
745 # Take raw method argument list and return ($obj, @args) in case
746 # the method was called upon an instance and (undef, @args) if
747 # it was called directly.
749 # This breaks inheritance. Oh well.
750 ref $_[0] eq 'Git' ?
@_ : (undef, @_);
753 # Check if the command id is something reasonable.
754 sub _check_valid_cmd
{
756 $cmd =~ /^[a-z0-9A-Z_-]+$/ or throw Error
::Simple
("bad command: $cmd");
759 # Common backend for the pipe creators.
760 sub _command_common_pipe
{
761 my $direction = shift;
762 my ($self, @p) = _maybe_self
(@_);
763 my (%opts, $cmd, @args);
765 ($cmd, @args) = @
{shift @p};
766 %opts = ref $p[0] ?
%{$p[0]} : @p;
770 _check_valid_cmd
($cmd);
773 if ($^O
eq 'MSWin32') {
775 #defined $opts{STDERR} and
776 # warn 'ignoring STDERR option - running w/ ActiveState';
777 $direction eq '-|' or
778 die 'input pipe for ActiveState not implemented';
779 # the strange construction with *ACPIPE is just to
780 # explain the tie below that we want to bind to
781 # a handle class, not scalar. It is not known if
782 # it is something specific to ActiveState Perl or
784 tie
(*ACPIPE
, 'Git::activestate_pipe', $cmd, @args);
788 my $pid = open($fh, $direction);
789 if (not defined $pid) {
790 throw Error
::Simple
("open failed: $!");
791 } elsif ($pid == 0) {
792 if (defined $opts{STDERR
}) {
796 open (STDERR
, '>&', $opts{STDERR
})
797 or die "dup failed: $!";
799 _cmd_exec
($self, $cmd, @args);
802 return wantarray ?
($fh, join(' ', $cmd, @args)) : $fh;
805 # When already in the subprocess, set up the appropriate state
806 # for the given repository and execute the git command.
808 my ($self, @args) = @_;
810 $self->repo_path() and $ENV{'GIT_DIR'} = $self->repo_path();
811 $self->wc_path() and chdir($self->wc_path());
812 $self->wc_subdir() and chdir($self->wc_subdir());
814 _execv_git_cmd
(@args);
815 die "exec failed: $!";
818 # Execute the given Git command ($_[0]) with arguments ($_[1..])
819 # by searching for it at proper places.
820 sub _execv_git_cmd
{ exec('git', @_); }
822 # Close pipe to a subprocess.
827 # It's just close, no point in fatalities
828 carp
"error closing pipe: $!";
830 # The caller should pepper this.
831 throw Git
::Error
::Command
($ctx, $?
>> 8);
833 # else we might e.g. closed a live stream; the command
834 # dying of SIGPIPE would drive us here.
842 # Pipe implementation for ActiveState Perl.
844 package Git
::activestate_pipe
;
848 my ($class, @params) = @_;
849 # FIXME: This is probably horrible idea and the thing will explode
850 # at the moment you give it arguments that require some quoting,
851 # but I have no ActiveState clue... --pasky
852 # Let's just hope ActiveState Perl does at least the quoting
854 my @data = qx{git
@params};
855 bless { i
=> 0, data
=> \
@data }, $class;
860 if ($self->{i
} >= scalar @
{$self->{data
}}) {
863 return $self->{'data'}->[ $self->{i
}++ ];
868 delete $self->{data
};
874 return ($self->{i
} >= scalar @
{$self->{data
}});
878 1; # Famous last words