/usr/share/perl5/Dist/Zilla/App/Command/build.pm is in libdist-zilla-perl 6.010-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 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 | use strict;
use warnings;
package Dist::Zilla::App::Command::build 6.010;
# ABSTRACT: build your dist
use Dist::Zilla::App -command;
#pod =head1 SYNOPSIS
#pod
#pod dzil build [ --trial ] [ --tgz | --no-tgz ] [ --in /path/to/build/dir ]
#pod
#pod =head1 DESCRIPTION
#pod
#pod This command is a very thin layer over the Dist::Zilla C<build> method, which
#pod does all the things required to build your distribution. By default, it will
#pod also archive your distribution and leave you with a complete, ready-to-release
#pod distribution tarball.
#pod
#pod To go a bit further in depth, the C<build> command will do two things:
#pod
#pod =over
#pod
#pod =item
#pod
#pod Generate a directory containing your module, C<Foo-0.100>. This directory is
#pod complete. You could create a gzipped tarball from this directory and upload it
#pod directly to C<PAUSE> if you so desired. You could C<cd> into this directory and
#pod test your module on Perl installations where you don't have C<Dist::Zilla>, for
#pod example.
#pod
#pod This is a default behavior of the C<build> command. You can alter where it puts
#pod the directory with C<--in /path/to/build/dir>.
#pod
#pod =item
#pod
#pod Generate a gzipped tarball of your module, C<Foo-0.100.tar.gz>. This file
#pod could be uploaded directly to C<PAUSE> to make a release of your module if you
#pod wanted. Or, you can test your module: C<cpanm --test-only Foo-0.100.tar.gz>.
#pod This is the same thing you would get if you compressed the directory described
#pod above.
#pod
#pod The gzipped tarball is generated by default, but if you don't want it to be
#pod generated, you can pass the C<--no-tgz> option. In that case, it would only
#pod generate the directory described above.
#pod
#pod =back
#pod
#pod Once you're done testing or publishing your build, you can clean up everything
#pod with a C<dzil clean>.
#pod
#pod =cut
sub abstract { 'build your dist' }
#pod =head1 EXAMPLE
#pod
#pod $ dzil build
#pod $ dzil build --no-tgz
#pod $ dzil build --in /path/to/build/dir
#pod
#pod =cut
sub opt_spec {
[ 'trial' => 'build a trial release that PAUSE will not index' ],
[ 'tgz!' => 'build a tarball (default behavior)', { default => 1 } ],
[ 'in=s' => 'the directory in which to build the distribution' ]
}
#pod =head1 OPTIONS
#pod
#pod =head2 --trial
#pod
#pod This will build a trial distribution. Among other things, it will generally
#pod mean that the built tarball's basename ends in F<-TRIAL>.
#pod
#pod =head2 --tgz | --no-tgz
#pod
#pod Builds a .tar.gz in your project directory after building the distribution.
#pod
#pod --tgz behaviour is by default, use --no-tgz to disable building an archive.
#pod
#pod =head2 --in
#pod
#pod Specifies the directory into which the distribution should be built. If
#pod necessary, the directory will be created. An archive will not be created.
#pod
#pod =cut
sub execute {
my ($self, $opt, $args) = @_;
if ($opt->in) {
require Path::Tiny;
die qq{using "--in ." would destroy your working directory!\n}
if Path::Tiny::path($opt->in)->absolute eq Path::Tiny::path('.')->absolute;
$self->zilla->build_in($opt->in);
} else {
my $method = $opt->tgz ? 'build_archive' : 'build';
my $zilla;
{
# isolate changes to RELEASE_STATUS to zilla construction
local $ENV{RELEASE_STATUS} = $ENV{RELEASE_STATUS};
$ENV{RELEASE_STATUS} = 'testing' if $opt->trial;
$zilla = $self->zilla;
}
$zilla->$method;
}
$self->zilla->log('built in ' . $self->zilla->built_in);
}
1;
__END__
=pod
=encoding UTF-8
=head1 NAME
Dist::Zilla::App::Command::build - build your dist
=head1 VERSION
version 6.010
=head1 SYNOPSIS
dzil build [ --trial ] [ --tgz | --no-tgz ] [ --in /path/to/build/dir ]
=head1 DESCRIPTION
This command is a very thin layer over the Dist::Zilla C<build> method, which
does all the things required to build your distribution. By default, it will
also archive your distribution and leave you with a complete, ready-to-release
distribution tarball.
To go a bit further in depth, the C<build> command will do two things:
=over
=item
Generate a directory containing your module, C<Foo-0.100>. This directory is
complete. You could create a gzipped tarball from this directory and upload it
directly to C<PAUSE> if you so desired. You could C<cd> into this directory and
test your module on Perl installations where you don't have C<Dist::Zilla>, for
example.
This is a default behavior of the C<build> command. You can alter where it puts
the directory with C<--in /path/to/build/dir>.
=item
Generate a gzipped tarball of your module, C<Foo-0.100.tar.gz>. This file
could be uploaded directly to C<PAUSE> to make a release of your module if you
wanted. Or, you can test your module: C<cpanm --test-only Foo-0.100.tar.gz>.
This is the same thing you would get if you compressed the directory described
above.
The gzipped tarball is generated by default, but if you don't want it to be
generated, you can pass the C<--no-tgz> option. In that case, it would only
generate the directory described above.
=back
Once you're done testing or publishing your build, you can clean up everything
with a C<dzil clean>.
=head1 EXAMPLE
$ dzil build
$ dzil build --no-tgz
$ dzil build --in /path/to/build/dir
=head1 OPTIONS
=head2 --trial
This will build a trial distribution. Among other things, it will generally
mean that the built tarball's basename ends in F<-TRIAL>.
=head2 --tgz | --no-tgz
Builds a .tar.gz in your project directory after building the distribution.
--tgz behaviour is by default, use --no-tgz to disable building an archive.
=head2 --in
Specifies the directory into which the distribution should be built. If
necessary, the directory will be created. An archive will not be created.
=head1 AUTHOR
Ricardo SIGNES 😏 <rjbs@cpan.org>
=head1 COPYRIGHT AND LICENSE
This software is copyright (c) 2017 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
|