view release on metacpan or  search on metacpan

bin/transpierce  view on Meta::CPAN

sub print_permissions
{
	my ($config) = @_;

	say "Files specified in the config file";
	foreach my $file (@$config) {
		say $file->{relpath};
		say "  mode -> $file->{chmod}";
		say "  uid -> $file->{chown}";
		say "  gid -> $file->{chgrp}";
		say '-------';
	}

	say '';
}

__END__

=head1 NAME

lib/App/Transpierce.pm  view on Meta::CPAN

=over

=item * lets you audit the contents of the files to see whether they do what is advertised and do not break anything else

=item * makes it trivial to do any modifications

=back

Both C<restore.sh> and C<deploy.sh> scripts copy each file back into their
original locations from the corresponding directory, then change their mode,
uid and gid back to what it was during the initialization. You might
B<require root permissions> to run those scripts, depending on files'
original locations and permissions.

C<diff.sh> script can be run to make sure file contents in C<restore> directory
do not differ from original files. It is recommended to do that before running
C<deploy.sh> script. If there are differences, it's possible that original
files were updated in the meantime and current working environment needs to be
initialized again.

=head2 Taking it with you