1 #@ conf.rc can be used adjust the set of desired features, paths, etc.
2 #@ You should have read `INSTALL' first.
4 #@ . This file is parsed by the shell: it is in sh(1), not in make(1) syntax.
5 #@ . Choosing one of the predefined CONFIG= sets overwrites a lot of items
6 #@ that can be set in here
7 #@ . Specifying settings on the command line will take precedence over the
8 #@ variables in here (correctly triggering build updates as necessary)
9 #@ . Using one of the predefined CONFIG= sets overrides anything else
10 #@ . You may NOT comment out anything in here -- if you want to disable a
11 #@ feature, simply set it to `0'. (It won't work properly otherwise!)
15 # The variables in here can be used to adjust the feature set of S-nail.
16 # Only if a variable is set to `1' it is treated as being `set'.
17 # Only a `set' variable will cause the possibly necessary feature tests to be
18 # performed, so as to detect wether the wanted feature really can be used
20 # S-nail automatically detects compilers and has a set of known compiler flags
21 # which work well. Since users should be able to define their own $CC, $CFLAGS
22 # and $LDFLAGS, however, it only uses the detected environment if the user
23 # forces their usage via setting WANT_AUTOCC=1. (Except for $CC, which is
24 # always set if it's empty or set to "cc".)
25 # Note: it is possible to add to the detected values by setting ADDCFLAGS="xy"
26 # and/or ADDLDFLAGS="xy" -- "configuration-has-changed" detection will work on
27 # the final $CC / $CFLAGS / $LDFLAGS, and thus will include those additions
30 # It is possible to compile S-nail as a "single-source", meaning that all
31 # source files are injected into a single compilation unit, which is then
32 # compiled. This allows the compiler to perform much more optimizations, and
33 # also reduces the management overhead that is used for / needed by the linker.
34 # Of course compiling such a large source requires a lot of memory by itself
35 # NOTE: experimental in that the feature is quite new -- it is thus not known
36 # wether some compilers may generate buggy code when compiling single-source
39 # Major switch to toggle *all* network related protocols (IMAP,POP3,SMTP) and
40 # related/dependent stuff (GSSAPI,SSL)
43 # If WANT_SOCKETS, should the IPv6 family of functions be searched for and
44 # compiled into the program if found?
46 # TODO S-nail does not yet support IPv6 address notation, as in, e.g.,
47 # TODO imaps://user1@::1 (or @[::1]), but it will happily establish a
48 # TODO connection to imaps://user1@host1 if host1 listens via IPv6
51 # Support for SecureSocketLayer (TransportLayerSecurity, TLS), i.e.,
52 # encrypted socket connections.
53 # This needs OpenSSL libraries (<http://www.openssl.org>; these should be
54 # installed by default on practically all operating systems today, though)
57 # Support for IMAP protocol? (Reading of mails directly on the server)
59 # Support for GSSAPI-based authentication, i.e., Kerberos V5 for IMAP?
60 # (This is disabled by default because it brings in a bunch of dependencies,
61 # and most people don't need it.)
64 # Support for POP3 protocol? (Download of mails via POP over the network)
67 # Support for SMTP protocol? (Directly sending mails over the network)
70 # Several facilities use the MD5 message digest, but for some of them it is
71 # only used for optional features (POP3: APOP authentification, IMAP: CRAM-MD5
72 # authentification, SMTP: CRAM-MD5 authentification).
73 # If you don't need those, you may exclude MD5 from S-nail.
74 # Note that WANT_MD5 is automatically turned off if its exclusion will only
75 # affect MIME boundary strings and Message-Id: fields
78 # Character set conversion enables reading and sending of mails in multiple
79 # character sets through usage of the iconv(3) library.
80 # Please read the manual section "Character sets" for the complete picture.
81 # This should usually be enabled
84 # IDNA (internationalized domain names for applications) offers users the
85 # possibility to use domain names in their native language, i.e., to use
86 # non-US-ASCII content, as in, e.g., <www.räksmörgåsa.example>, which the IDNA
87 # algorithm would convert to <www.xn--rksmrgsa-0zap8p.example>. :)
88 # This needs the GNU Libidn library (<https://www.gnu.org/software/libidn/>)
91 # Command line editing and -history.
92 # S-nail actually supports three different command line editors, one builtin
93 # and two fully fledged external libraries which may offer a slightly better
94 # user experience at the cost of more memory usage and CPU time.
95 # Note that these are tested in shown order, and each desired one must be
98 # The GNU readline(3) compatible interface
100 # Command line editing via BSD editline(3)
102 # If ISO C (ISO/IEC 9899:1990/Amendment 1:1995) is supported on the system
103 # then our builtin NCL (Nail Command Line editor) version can be used.
104 # It is documented in the manual section "Command line editor" (in ./nail.1)
108 # For all command line editors we optionally support history
110 # For the NCL command line editor we optionally support "expand-on-tabulator".
111 # Turning it off shrinks the binary. Please see the respective manual entry
114 # Interaction with a spam email filter is possible.
115 # Refer to all commands with a `spam' prefix, and see the manual section
116 # "Handling spam" (`./nail.1')
119 # If given an optional argument the `help' command will print a help string
120 # only for the mentioned command; those strings take up space and so one may
121 # disable this feature.
124 # A simple line-based quoting mechanism can be made available via the
125 # *quote-fold* mechanism.
126 # This will be turned off automatically if the required character
127 # classification is not available on the host.
128 # TODO shouldn't wrap lines when only WS or a NL-escaping \ follows
131 ## PATHS AND PROGRAMS ##
133 # General prefix where S-nail should be installed
136 # Fine tune individual locations, normally under $PREFIX
137 # . the place of the S-nail program
138 BINDIR="${PREFIX}/bin"
140 MANDIR="${PREFIX}/man"
141 # . of the exemplary resource file
142 SYSCONFDIR="${PREFIX}/etc"
144 # This variable is prepended to all the paths from above at installation time;
145 # this feature can be used for, e.g., package building: if $PREFIX is
146 # `/usr/local', but $DESTDIR is set to, say, `here', then S-nail will still
147 # think its $PREFIX is `/usr/local' whereis the build system will instead use
151 # The directory where the local mail system stores user mail (mbox) files.
152 # (Only of interest if the local mail system is used)
155 # Path to the local MTA (Mail Transport Agent).
156 # (Only of interest if the local mail system is used)
157 SENDMAIL=/usr/sbin/sendmail
159 # Today a lot of systems no longer use sendmail(1), but a different MTA.
160 # To ensure compatibility with sendmail(1), a system called mailwrapper(8) is
161 # used, which selects the required service by looking at the name by which the
162 # program actually has been invoked.
163 # This variable can be used to adjust this name as necessary
164 # (Only of interest if the local mail system is used)
165 SENDMAIL_PROGNAME=sendmail
167 # Fallback sh(1) path.
168 # Note that it is not guaranteed that *all* uses of the shell use this, but it
169 # may actually happen that execlp(2) will need to fallback to its own one.
170 # (Note: this is named XSHELL so that it doesn't clash with the POSIX
171 # standard $SHELL, which would effectively cause this setting to be ignored)
174 # The default *LISTER* (in the $PATH).
175 # (Note: this is named XLISTER so that it doesn't clash with the POSIX
176 # standard $LISTER, which would effectively cause this setting to be ignored)
179 # The default *PAGER* (in the $PATH).
180 # (Note: this is named XPAGER so that it doesn't clash with the POSIX standard
181 # $PAGER, which would effectively cause this setting to be ignored)
186 ## Normal users should not need to read any further
188 ## PATHS AND PROGRAMS, DEVELOPMENT ##
190 # To ease the life of forkers and packagers "our" name can be changed.
191 # The name is build by concatenating $SID and $NAIL, i.e., $(SID)$(NAIL).
192 # Note that the final string must be longer than two characters and may not
193 # contain any whitespace
197 # The location of the exemplary resource template.
198 # Note 1: it's not overwritten if it yet exists!
199 # Note 2: `make install' assumes it's under $SYSCONFDIR!
200 SYSCONFRC="${SYSCONFDIR}/${SID}${NAIL}.rc"
202 ## FEATURE SET, DEVELOPMENT ##
204 # Use debug compiler flags, enable some additional commands (like `sstats',
205 # `smemtrace'), some code assertions, possibly experimental code etc.
206 # Note that setting this also enables our own memory canaries, which require
207 # a rather large amount of runtime memory, and forcefully disables alloca(3)
208 # stack memory usage (see WANT_NOALLOCA below), so as to be able to track usage
209 # of stack memory via our memory canaries
212 # We ship with our own small and efficient getopt(3) implementation;
213 # set this to always choose that without even checking for another one
216 # The codebase makes a lot of use of alloca(3), and this will remain since
217 # S-nail will continue to be compliant to ISO C89, which has no variable
218 # arrays, etc. For testing purposes it is however nice to use the much slower
219 # normal S-nail heap memory allocator instead.
220 # Note: this will be forcefully set (again) if WANT_DEBUG=1
221 WANT_NOALLOCA="${WANT_DEBUG}"
223 # vim:set fenc=utf-8 syntax=conf:s-it-mode