- to the ./configure command or pass this in the environment.
- This pretends that no Python interpreter were installed.
-
-- the Makefile generates a two-line "fetchmailconf" /bin/sh wrapper
- script that executes the actual fetchmailconf.py with the python
- installation found at configuration time, so that users can still type
- "fetchmailconf" rather than "python fetchmailconf"
-
-- note that fetchmailconf.py supports a few command line arguments, so
- if you use local wrapper scripts, be sure they pass on their own
- arguments properly. Remember to use "$@" (with quotes) in shells, not $*.
-
-- there is now a dummy fetchmailconf manual page which will just source
- (roff's ".so" command) the fetchmail manual page for now. You can of
- course keep your symlinks in place and ignore this dummy. IF you
- install the dummy and compress your man pages, be sure to test "man
- fetchmailconf", on some systems, you'll need to adjust the ".so"
- command to point to the compressed version.
+
+ to the ./configure command or pass this in the environment. This pretends
+ that no Python interpreter were installed.
+
+- The Makefile generates a two-line "fetchmailconf" /bin/sh wrapper script that
+ executes the actual fetchmailconf.py with the python installation found at
+ configuration time, so that users can still type "fetchmailconf" rather than
+ "python fetchmailconf".
+
+- Note that fetchmailconf.py supports a few command line arguments, so if you
+ use local wrapper scripts, be sure they pass on their own arguments properly.
+ Remember to use "$@" (with quotes) in shells, not $*.
+
+- There is now a dummy fetchmailconf manual page which will just source (roff's
+ ".so" command) the fetchmail manual page for now. You can of course keep your
+ symlinks in place and ignore this dummy. IF you install the dummy and
+ compress your man pages, be sure to test "man fetchmailconf", on some
+ systems, you'll need to adjust the ".so" command to point to the compressed
+ version.