docs/tutorial.html
examples/bbtidy.pl
examples/break_long_quotes.pl
+examples/delete_ending_blank_lines.pl
examples/ex_mp.pl
examples/filter_example.in
examples/filter_example.pl
t/snippets11.t
t/snippets12.t
t/snippets13.t
+t/snippets14.t
+t/snippets15.t
t/snippets2.t
t/snippets3.t
t/snippets4.t
t/snippets7.t
t/snippets8.t
t/snippets9.t
+t/test-eol.t
t/test.t
t/testsa.t
t/testss.t
\#$
\b\.#
\.bak$
+\.ba1$
\.tmp$
\.log$
\.archive$
# These are the main steps, in approximate order, for making a new version
# Note: Since perl critic is in the .tidyallrc, a separate 'PC' step is not
# needed
-my $rsteps = [qw( CHK V PC TIDY T CL DOCS DIST)];
+my $rsteps = [qw( CHK V PC TIDY T CL DOCS MANIFEST DIST)];
my $rstatus = {};
foreach my $step ( @{$rsteps} ) { $rstatus->{$step} = 'TBD' }
'TIDY' => \&run_tidyall,
'T' => \&make_tests,
'DOCS' => \&make_docs,
+ 'MANIFEST' => \&make_manifest,
'DIST' => \&make_dist,
'CL' => sub {openurl($changelog)},
'LOG' => sub { openurl($logfile) },
Perltidy Build Main Menu - Case Insensitive
-------------------------------------------
-A - run All Steps...
-chk - view release CHecKlist status: $rstatus->{'CHK'}
-v - check/update Version Number status: $rstatus->{'V'}
-tidy - run tidyall (tidy & critic) status: $rstatus->{'TIDY'}
-pc - run PerlCritic (critic only) status: $rstatus->{'PC'}
-t - make Tests status: $rstatus->{'T'}
-cl - review/edit CHANGES.md status: $rstatus->{'CL'}
-docs - check and process POD & html status: $rstatus->{'DOCS'}
-dist - make a Distribution tar.gz status: $rstatus->{'DIST'}
-log - view Log file
-html - view html files
+A - run All Steps...
+chk - view release CHecKlist status: $rstatus->{'CHK'}
+v - check/update Version Number status: $rstatus->{'V'}
+tidy - run tidyall (tidy & critic) status: $rstatus->{'TIDY'}
+pc - run PerlCritic (critic only) status: $rstatus->{'PC'}
+t - make Tests status: $rstatus->{'T'}
+cl - review/edit CHANGES.md status: $rstatus->{'CL'}
+manifest - make MANIFEST status: $rstatus->{'MANIFEST'}
+docs - check and process POD & html status: $rstatus->{'DOCS'}
+dist - make a Distribution tar.gz status: $rstatus->{'DIST'}
+log - view Log file
+html - view html files
q,x - eXit
return;
}
+sub make_manifest {
+
+ # FIXME: show differences between old and new manifest
+ my $result = sys_command("make manifest");
+ print $result;
+ my $status = "OK";
+ $rstatus->{'MANIFEST'} = $status;
+ hitcr();
+ return;
+}
+
sub make_dist {
my $result;
}
}
- # Make the output file for read + write unless we are in -b mode.
- # Explanation: perltidy does not unlink existing output
- # files before writing to them, for safety. If a designated
- # output file exists and is not writable, perltidy will halt.
- # This can prevent a data loss if a user
- # accidentally enters "perltidy infile -o
- # important_ro_file", or "perltidy infile -st
- # >important_ro_file". But it also means that perltidy can
- # get locked out of rerunning unless it marks its own
- # output files writable. The alternative, of always
- # unlinking the designated output
- # file, is less safe and not always possible, except in -b
- # mode, where there is an assumption that a previous backup
- # can be unlinked even if not writable.
+ # Make the output file for rw unless we are in -b mode.
+ # Explanation: perltidy does not unlink existing output
+ # files before writing to them, for safety. If a
+ # designated output file exists and is not writable,
+ # perltidy will halt. This can prevent a data loss if a
+ # user accidentally enters "perltidy infile -o
+ # important_ro_file", or "perltidy infile -st
+ # >important_ro_file". But it also means that perltidy can
+ # get locked out of rerunning unless it marks its own
+ # output files writable. The alternative, of always
+ # unlinking the designated output file, is less safe and
+ # not always possible, except in -b mode, where there is an
+ # assumption that a previous backup can be unlinked even if
+ # not writable.
if ( !$in_place_modify ) {
$output_file_permissions |= oct(600);
}