/usr/share/perl5/Dist/Zilla/App/Command/run.pm is in libdist-zilla-perl 5.043-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 | use strict;
use warnings;
package Dist::Zilla::App::Command::run;
# ABSTRACT: run stuff in a dir where your dist is built
$Dist::Zilla::App::Command::run::VERSION = '5.043';
use Dist::Zilla::App -command;
#pod =head1 SYNOPSIS
#pod
#pod $ dzil run ./bin/myscript
#pod $ dzil run prove -bv t/mytest.t
#pod $ dzil run bash
#pod
#pod =head1 DESCRIPTION
#pod
#pod This command will build your dist with Dist::Zilla, then build the
#pod distribution and then run a command in the build directory. It's something
#pod like doing this:
#pod
#pod dzil build
#pod rsync -avp My-Project-version/ .build/
#pod cd .build
#pod perl Makefile.PL # or perl Build.PL
#pod make # or ./Build
#pod export PERL5LIB=$PWD/blib/lib:$PWD/blib/arch
#pod <your command as defined by rest of params>
#pod
#pod Except for the fact it's built directly in a subdir of .build (like
#pod F<.build/69105y2>).
#pod
#pod A command returning with an non-zero error code will left the build directory
#pod behind for analysis, and C<dzil> will exit with a non-zero status. Otherwise,
#pod the build directory will be removed and dzil will exit with status zero.
#pod
#pod If no run command is provided, a new default shell is invoked. This can be
#pod useful for testing your distribution as if it were installed.
#pod
#pod =cut
sub abstract { 'run stuff in a dir where your dist is built' }
sub opt_spec {
[ 'build!' => 'do the Build actions before running the command; done by default',
{ default => 1 } ],
}
sub description {
"This will build your dist and run the given 'command' in the build dir.\n" .
"If no command was specified, your shell will be run there instead."
}
sub usage_desc {
return '%c run %o [ command [ arg1 arg2 ... ] ]';
}
sub execute {
my ($self, $opt, $args) = @_;
unless (@$args) {
my $envname = $^O eq 'MSWin32' ? 'COMSPEC' : 'SHELL';
unless ($ENV{$envname}) {
$self->usage_error("no command supplied to run and no \$$envname set");
}
$args = [ $ENV{$envname} ];
$self->log("no command supplied to run so using \$$envname: $args->[0]");
}
$self->zilla->run_in_build($args, { build => $opt->build });
}
1;
__END__
=pod
=encoding UTF-8
=head1 NAME
Dist::Zilla::App::Command::run - run stuff in a dir where your dist is built
=head1 VERSION
version 5.043
=head1 SYNOPSIS
$ dzil run ./bin/myscript
$ dzil run prove -bv t/mytest.t
$ dzil run bash
=head1 DESCRIPTION
This command will build your dist with Dist::Zilla, then build the
distribution and then run a command in the build directory. It's something
like doing this:
dzil build
rsync -avp My-Project-version/ .build/
cd .build
perl Makefile.PL # or perl Build.PL
make # or ./Build
export PERL5LIB=$PWD/blib/lib:$PWD/blib/arch
<your command as defined by rest of params>
Except for the fact it's built directly in a subdir of .build (like
F<.build/69105y2>).
A command returning with an non-zero error code will left the build directory
behind for analysis, and C<dzil> will exit with a non-zero status. Otherwise,
the build directory will be removed and dzil will exit with status zero.
If no run command is provided, a new default shell is invoked. This can be
useful for testing your distribution as if it were installed.
=head1 AUTHOR
Ricardo SIGNES <rjbs@cpan.org>
=head1 COPYRIGHT AND LICENSE
This software is copyright (c) 2016 by Ricardo SIGNES.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
=cut
|