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
28 # Thus: set this to 0 and use your normal $CC / $CFLAGS / $LDFLAGS, set this to
29 # 1 and pass additional flags via ADDCFLAGS / ADDLDFLAGS.
30 # Whatever you do, the configuration is fixated and updates will force rebuilds
33 # It is possible to compile S-nail as a "single-source", meaning that all
34 # source files are injected into a single compilation unit, which is then
35 # compiled. This allows the compiler to perform much more optimizations, and
36 # also reduces the management overhead that is used for / needed by the linker.
37 # Of course compiling such a large source requires a lot of memory by itself
38 # NOTE: experimental in that the feature is quite new -- it is thus not known
39 # wether some compilers may generate buggy code when compiling single-source
42 # Major switch to toggle *all* network related protocols (IMAP,POP3,SMTP) and
43 # related/dependent stuff (GSSAPI,SSL)
46 # If WANT_SOCKETS, should the IPv6 family of functions be searched for and
47 # compiled into the program if found?
49 # TODO S-nail does not yet support IPv6 address notation, as in, e.g.,
50 # TODO imaps://user1@::1 (or @[::1]), but it will happily establish a
51 # TODO connection to imaps://user1@host1 if host1 listens via IPv6
54 # Support for SecureSocketLayer (TransportLayerSecurity, TLS), i.e.,
55 # encrypted socket connections.
56 # This needs OpenSSL libraries (<http://www.openssl.org>; these should be
57 # installed by default on practically all operating systems today, though)
60 # Support for IMAP protocol? (Reading of mails directly on the server)
62 # Support for GSSAPI-based authentication, i.e., Kerberos V5 for IMAP?
63 # (This is disabled by default because it brings in a bunch of dependencies,
64 # and most people don't need it.)
67 # Support for POP3 protocol? (Download of mails via POP over the network)
70 # Support for SMTP protocol? (Directly sending mails over the network)
73 # Several facilities use the MD5 message digest, but for some of them it is
74 # only used for optional features (POP3: APOP authentification, IMAP: CRAM-MD5
75 # authentification, SMTP: CRAM-MD5 authentification).
76 # If you don't need those, you may exclude MD5 from S-nail.
77 # Note that WANT_MD5 is automatically turned off if its exclusion will only
78 # affect MIME boundary strings and Message-Id: fields
81 # Character set conversion enables reading and sending of mails in multiple
82 # character sets through usage of the iconv(3) library.
83 # Please read the manual section "Character sets" for the complete picture.
84 # This should usually be enabled
87 # IDNA (internationalized domain names for applications) offers users the
88 # possibility to use domain names in their native language, i.e., to use
89 # non-US-ASCII content, as in, e.g., <www.räksmörgåsa.example>, which the IDNA
90 # algorithm would convert to <www.xn--rksmrgsa-0zap8p.example>. :)
91 # This needs the GNU Libidn library (<https://www.gnu.org/software/libidn/>)
94 # IMAP-style SEARCH expressions can be supported.
95 # This addressing mode is available with all types of folders; for folders not
96 # located on IMAP servers, or for servers unable to execute the SEARCH command,
97 # the search is performed locally
100 # Regular expression (re_format(7)) support for searches.
103 # Command line editing and -history.
104 # S-nail actually supports three different command line editors, one builtin
105 # and two fully fledged external libraries which may offer a slightly better
106 # user experience at the cost of more memory usage and CPU time; also the
107 # interactive behaviour may not be one-to-one to what is documented.
108 # Note that these are tested in shown order, and each desired one must be
111 # The GNU readline(3) compatible interface
113 # Command line editing via BSD editline(3)
115 # If ISO C (ISO/IEC 9899:1990/Amendment 1:1995) is supported on the system
116 # then our builtin NCL (Nail Command Line editor) version can be used.
117 # It is documented in the manual section "Command line editor" (in ./nail.1)
121 # For all command line editors we optionally support history management
123 # For the NCL command line editor we optionally support "expand-on-tabulator".
124 # Turning it off shrinks the binary. Please see the respective manual entry
127 # Interaction with a spam email filter is possible.
128 # Refer to all commands with a `spam' prefix, and see the manual section
129 # "Handling spam" (`./nail.1')
132 # If given an optional argument the `help' command will print a help string
133 # only for the mentioned command; those strings take up space and so one may
134 # disable this feature
137 # A simple line-based quoting mechanism can be made available via the
138 # *quote-fold* mechanism.
139 # This will be turned off automatically if the required character
140 # classification is not available on the host.
141 # TODO shouldn't wrap lines when only WS or a NL-escaping \ follows
144 # A simple form of coloured output can optionally be produced (see manual)
147 ## PATHS AND PROGRAMS ##
149 # General prefix where S-nail should be installed
152 # Fine tune individual locations, normally under $PREFIX
153 # . the place of the S-nail program
154 BINDIR="${PREFIX}/bin"
156 MANDIR="${PREFIX}/man"
157 # . of the exemplary resource file
158 SYSCONFDIR="${PREFIX}/etc"
160 # This variable is prepended to all the paths from above at installation time;
161 # this feature can be used for, e.g., package building: if $PREFIX is
162 # `/usr/local', but $DESTDIR is set to, say, `here', then S-nail will still
163 # think its $PREFIX is `/usr/local' whereis the build system will instead use
167 # The directory where the local mail system stores user mail (mbox) files.
168 # (Only of interest if the local mail system is used)
171 # Path to the local MTA (Mail Transport Agent).
172 # (Only of interest if the local mail system is used)
173 SENDMAIL=/usr/sbin/sendmail
175 # Today a lot of systems no longer use sendmail(1), but a different MTA.
176 # To ensure compatibility with sendmail(1), a system called mailwrapper(8) is
177 # used, which selects the required service by looking at the name by which the
178 # program actually has been invoked.
179 # This variable can be used to adjust this name as necessary
180 # (Only of interest if the local mail system is used)
181 SENDMAIL_PROGNAME=sendmail
183 # Fallback sh(1) path.
184 # Note that it is not guaranteed that *all* uses of the shell use this, but it
185 # may actually happen that execlp(2) will need to fallback to its own one.
186 # (Note: this is named XSHELL so that it doesn't clash with the POSIX
187 # standard $SHELL, which would effectively cause this setting to be ignored)
190 # The default *LISTER* (in the $PATH).
191 # (Note: this is named XLISTER so that it doesn't clash with the POSIX
192 # standard $LISTER, which would effectively cause this setting to be ignored)
195 # The default *PAGER* (in the $PATH).
196 # (Note: this is named XPAGER so that it doesn't clash with the POSIX standard
197 # $PAGER, which would effectively cause this setting to be ignored)
200 # The following tools may be provided a.k.a. overwritten, `command -v NAME`
201 # is used to query the utility otherwise:
202 # MAKE=, STRIP=, awk=, cat=, chmod=, cp=, cmp=, grep=, mkdir=, mv=, tee=
204 # Note that rm(1) and sed(1) are needed before this file is read, all other
205 # utilities will be checked afterwards only.
206 # For cross-compilation setting MAKE= and STRIP= may be necessary
210 ## Normal users should not need to read any further
212 ## PATHS AND PROGRAMS, DEVELOPMENT ##
214 # To ease the life of forkers and packagers "our" name can be changed.
215 # The name is build by concatenating $SID and $NAIL, i.e., $(SID)$(NAIL).
216 # Note that the final string must be longer than two characters and may not
217 # contain any whitespace
221 # The location of the exemplary resource template.
222 # Note 1: it's not overwritten if it yet exists!
223 # Note 2: `make install' assumes it's under $SYSCONFDIR!
224 SYSCONFRC="${SYSCONFDIR}/${SID}${NAIL}.rc"
226 ## FEATURE SET, DEVELOPMENT ##
228 # Use debug compiler flags, enable some additional commands (like `sstats',
229 # `smemtrace'), some code assertions, possibly experimental code etc.
230 # Note that setting this also enables our own memory canaries, which require
231 # a rather large amount of runtime memory, and forcefully disables alloca(3)
232 # stack memory usage (see WANT_NOALLOCA below), so as to be able to track usage
233 # of stack memory via our memory canaries
236 # We ship with our own small and efficient getopt(3) implementation;
237 # set this to always choose that without even checking for another one
240 # The codebase makes a lot of use of alloca(3), and this will remain since
241 # S-nail will continue to be compliant to ISO C89, which has no variable
242 # arrays, etc. For testing purposes it is however nice to use the much slower
243 # normal S-nail heap memory allocator instead.
244 # Note: this will be forcefully set (again) if WANT_DEBUG=1
245 WANT_NOALLOCA="${WANT_DEBUG}"
247 # vim:set fenc=utf-8 syntax=conf:s-it-mode