Document the new options: --modid-path, --load-untested

diff --git a/src/libcaptive/client/options.pod.pl.in b/src/libcaptive/client/options.pod.pl.in
index 3355c86..260b551 100644 (file)
--- a/src/libcaptive/client/options.pod.pl.in
+++ b/src/libcaptive/client/options.pod.pl.in
@@ -27,6 +27,9 @@ use warnings;
 my $vardir='@localstatedir@/lib/@PACKAGE@';
 $vardir=~s#\$\Q{prefix}\E#'@prefix@';#ge;
 $vardir="/var/lib/@PACKAGE@" if $vardir=~/^@/;
+my $sysconfdir='@sysconfdir@';
+$sysconfdir=~s#\$\Q{prefix}\E#'@prefix@';#ge;
+$sysconfdir="/etc" if $sysconfdir=~/^@/;
 my $sbindir='@sbindir@';
 $sbindir=~s#\$\Q{exec_prefix}\E#'@exec_prefix@';#ge;
 $sbindir=~s#\$\Q{prefix}\E#'@prefix@';#ge;
@@ -64,6 +67,26 @@ print <<'POD_EOF';
 here.
 
 
+=item B<--modid-path>=B<pathname>
+
+Pathname to the B<.captivemodid.xml> database of existing W32 module
+identifications. The default used one is:
+POD_EOF
+print "B<$sysconfdir/w32-mod-id.captivemodid.xml>\n";
+print <<'POD_EOF';
+You must have this database update for any W32 binary module you are using.
+If you miss such database you may also try to use B<--load-untested> below.
+
+
+=item B<--load-untested>
+
+Load tthe W32 modules despite they may not match the current B<--modid-path>
+identifications database. If you use this option Captive may fail very easily
+as such module was never tested before the release and may need some
+compatibility updates. Still no data should be corrupted even if using this
+B<--load-untested> option.
+
+
 =item B<--ro>
 
 Read/write mode: Any write access will be forbidden. You should set this mode