lumia

Archive checksum manager
git clone git://lumidify.org/lumia.git
Log | Files | Refs | README | LICENSE

commit 0ca1ccf7f2e9e3587700434fa6f773a291903bcf
parent e46785870f510106749e20fd9fe5e242f381717c
Author: lumidify <nobody@lumidify.org>
Date:   Sat, 28 Mar 2020 18:24:22 +0100

Clarify documentation

Diffstat:
Mlumia.pl | 9+++++++++
1 file changed, 9 insertions(+), 0 deletions(-)

diff --git a/lumia.pl b/lumia.pl @@ -1137,6 +1137,9 @@ error and the user answered "n" when prompted), a warning message is printed, but the files B<are removed from the database> (if the database can be written to). +It is an error if there are no checksum database files in the directory +of a file named on the command line. + C<-f> is passed through to the system C<rm> command. =item B<cp> [-vf] source target @@ -1150,6 +1153,9 @@ which is then copied to the target. If the last argument is a directory, all source arguments are copied into it. +It is an error if a source or destination directory does not contain any +checksum database files. + B<cp> will issue a warning and skip to the next argument if it is asked to merge a directory with an already existing directory. For instance, attempting to run C<cp dir1 dir2>, where C<dir2> already contains a directory named @@ -1178,6 +1184,9 @@ argument, which is renamed to the target name. If the last argument is an existing directory, all source arguments are moved into it. +It is an error if a source or destination directory does not contain any +checksum database files. + B<mv> behaves the same as B<rm> with regards to checking if the source file is still present after the operation and other error handling.