Acme-CPANModules-PERLANCAR-RsyncEnhancements
view release on metacpan or search on metacpan
a) cause the modified files to carry prominent notices stating that
you changed the files and the date of any change; and
b) cause the whole of any work that you distribute or publish, that
in whole or in part contains the Program or any part thereof, either
with or without modifications, to be licensed at no charge to all
third parties under the terms of this General Public License (except
that you may choose to grant warranty protection to some or all
third parties, at your option).
c) If the modified program normally reads commands interactively when
run, you must cause it, when started running for such interactive use
in the simplest and most usual way, to print or display an
announcement including an appropriate copyright notice and a notice
that there is no warranty (or else, saying that you provide a
warranty) and that users may redistribute the program under these
conditions, and telling the user how to view a copy of this General
Public License.
d) You may charge a fee for the physical act of transferring a
copy, and you may at your option offer warranty protection in
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19xx name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License. Of course, the
commands you use may be called something other than `show w' and `show
c'; they could even be mouse-clicks or menu items--whatever suits your
program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
program `Gnomovision' (a program to direct compilers to make passes
at assemblers) written by James Hacker.
"class" : "Pod::Weaver::Section::Region",
"name" : "@Author::PERLANCAR/postlude",
"version" : "4.015"
},
{
"class" : "Pod::Weaver::Section::Completion::GetoptLongComplete",
"name" : "@Author::PERLANCAR/Completion::GetoptLongComplete",
"version" : "0.08"
},
{
"class" : "Pod::Weaver::Section::Completion::GetoptLongSubcommand",
"name" : "@Author::PERLANCAR/Completion::GetoptLongSubcommand",
"version" : "0.04"
},
{
"class" : "Pod::Weaver::Section::Completion::GetoptLongMore",
"name" : "@Author::PERLANCAR/Completion::GetoptLongMore",
"version" : "0.001"
},
{
"class" : "Pod::Weaver::Section::Homepage::DefaultCPAN",
"name" : "@Author::PERLANCAR/Homepage::DefaultCPAN",
version: '4.015'
-
class: Pod::Weaver::Section::Region
name: '@Author::PERLANCAR/postlude'
version: '4.015'
-
class: Pod::Weaver::Section::Completion::GetoptLongComplete
name: '@Author::PERLANCAR/Completion::GetoptLongComplete'
version: '0.08'
-
class: Pod::Weaver::Section::Completion::GetoptLongSubcommand
name: '@Author::PERLANCAR/Completion::GetoptLongSubcommand'
version: '0.04'
-
class: Pod::Weaver::Section::Completion::GetoptLongMore
name: '@Author::PERLANCAR/Completion::GetoptLongMore'
version: '0.001'
-
class: Pod::Weaver::Section::Homepage::DefaultCPAN
name: '@Author::PERLANCAR/Homepage::DefaultCPAN'
version: '0.05'
-
slower (because it requires recording states in both sides) or
requires more specific tools (like version control system). In
simpler cases, when updates only happen in one side, you can perform
two-way syncing by just checking that: the side that has the newest
file "wins" (is sync-ed to the "losing" side). This script checks
that condition.
* App::rsync::retry
Rsync can resume a partial sync, but does not automatically retries.
An annoying thing is invoking an rsync command to sync a large tree,
leaving the computer for the day, then returning the following day
hoping the transfer would be completed, only to see that it failed
early because of a network hiccup. This wrapper automatically
retries rsync when there is a transfer error.
* App::rsynccolor
This wrapper adds some color to the rsync output, particularly
giving a red to deletion, so you can spot deletion more easily.
Particularly handy if you use it with the "-n" ("--dry-run") option.
lib/Acme/CPANModules/PERLANCAR/RsyncEnhancements.pm view on Meta::CPAN
the newest file "wins" (is sync-ed to the "losing" side). This script checks
that condition.
_
},
{
module => "App::rsync::retry",
description => <<'_',
Rsync can resume a partial sync, but does not automatically retries. An annoying
thing is invoking an rsync command to sync a large tree, leaving the computer
for the day, then returning the following day hoping the transfer would be
completed, only to see that it failed early because of a network hiccup. This
wrapper automatically retries rsync when there is a transfer error.
_
},
{
module => "App::rsynccolor",
description => <<'_',
lib/Acme/CPANModules/PERLANCAR/RsyncEnhancements.pm view on Meta::CPAN
it requires recording states in both sides) or requires more specific tools
(like version control system). In simpler cases, when updates only happen in one
side, you can perform two-way syncing by just checking that: the side that has
the newest file "wins" (is sync-ed to the "losing" side). This script checks
that condition.
=item * L<App::rsync::retry>
Rsync can resume a partial sync, but does not automatically retries. An annoying
thing is invoking an rsync command to sync a large tree, leaving the computer
for the day, then returning the following day hoping the transfer would be
completed, only to see that it failed early because of a network hiccup. This
wrapper automatically retries rsync when there is a transfer error.
=item * L<App::rsynccolor>
This wrapper adds some color to the rsync output, particularly giving a red to
deletion, so you can spot deletion more easily. Particularly handy if you use it
with the C<-n> (C<--dry-run>) option.
t/00-compile.t view on Meta::CPAN
use File::Spec;
use IPC::Open3;
use IO::Handle;
open my $stdin, '<', File::Spec->devnull or die "can't open devnull: $!";
my @warnings;
for my $lib (@module_files)
{
# see L<perlfaq8/How can I capture STDERR from an external command?>
my $stderr = IO::Handle->new;
diag('Running: ', join(', ', map { my $str = $_; $str =~ s/'/\\'/g; q{'} . $str . q{'} }
$^X, @switches, '-e', "require q[$lib]"))
if $ENV{PERL_COMPILE_TEST_DEBUG};
my $pid = open3($stdin, '>&STDERR', $stderr, $^X, @switches, '-e', "require q[$lib]");
binmode $stderr, ':crlf' if $^O eq 'MSWin32';
my @_warnings = <$stderr>;
waitpid($pid, 0);
( run in 0.864 second using v1.01-cache-2.11-cpan-2e0ccfb7a10 )