99c6c22267
1) libsaslc is an SASL client only. 2) dovecot is an SASL server only. 3) cyrus-sasl is both a client and a server. 4) postfix allows us to have multiple SASL servers and clients. 5) The SASL server to use at runtime is determined by the setting of "smtpd_sasl_type" in main.cf (note that is smtpd_ not smtp_). If that is not set, then it defaults to the value of DEF_SERVER_SASL_TYPE at build time, which if not set, defaults to "cyrus". See postfix/dist/src/global/mail_params.h. 6) The SASL client to use at runtime is determined by the setting of "smtp_sasl_type" in main.cf. If that is not set, then it defaults to the value of DEF_CLIENT_SASL_TYPE at build time, which if not set, defaults to "cyrus". See postfix/dist/src/global/mail_params.h. 7) If MKCRYPTO is "no", libsaslc will not link as it requires the crypto libraries, so libsaslc cannot be enabled (as it was before) without crypto. 8) I have made the definition of DEF_CLIENT_SASL_TYPE conditional on MKCRYPTO due to (7). Without crypto it will default to cyrus. 9) HAVE_CYRUS_SASL is _never_ defined during a normal build and _never_ should be! It is there for the convenience of users who wish to install cyrus-sasl and rebuild postfix with it. It is also very useful for testing if it is suspected that something might be wrong with libsaslc. PLEASE DO NOT REMOVE IT! |
||
---|---|---|
.. | ||
apache2 | ||
atheros | ||
bsd | ||
cddl | ||
gpl2 | ||
gpl3 | ||
historical | ||
ibm-public | ||
intel-fw-eula | ||
intel-fw-public | ||
intel-public | ||
mit | ||
public-domain | ||
zlib/pigz | ||
Makefile | ||
README |
$NetBSD: README,v 1.14 2010/11/03 18:52:44 christos Exp $ Organization of Sources: This directory hierarchy is using an organization that separates source for programs that we have obtained from external third parties (where NetBSD is not the primary maintainer) from the system source. The hierarchy is grouped by license, and then package per license, and is organized as follows: external/ Makefile Descend into the license sub-directories. <license>/ Per-license sub-directories. Makefile Descend into the package sub-directories. <package>/ Per-package sub-directories. Makefile Build the package. dist/ The third-party source for a given package. bin/ lib/ sbin/ BSD makefiles "reach over" from these into "../dist/". This arrangement allows for packages to be easily disabled or excised as necessary, either on a per-license or per-package basis. The licenses currently used are: apache2 Apache 2.0 license. http://www.opensource.org/licenses/apache2.0.php atheros Atheros License. bsd BSD (or equivalent) licensed software, possibly with the "advertising clause". http://www.opensource.org/licenses/bsd-license.php cddl Common Development and Distribution License (the sun license which is based on the Mozilla Public License version 1.1). http://www.opensource.org/licenses/cddl1.php gpl2 GNU Public License, version 2 (or earlier). http://www.opensource.org/licenses/gpl-2.0.php gpl3 GNU Public License, version 3. http://www.opensource.org/licenses/gpl-3.0.html historical Lucent's old license: http://www.opensource.org/licenses/historical.php ibm-public IBM's public license: http://www.opensource.org/licenses/ibmpl.php intel-fw-eula Intel firmware license with redistribution restricted to OEM. intel-fw-public Intel firmware license permitting redistribution with terms similar to BSD licensed software. intel-public Intel license permitting redistribution with terms similar to BSD licensed software. mit MIT (X11) style license. http://www.opensource.org/licenses/mit-license.php public-domain Non-license for code that has been explicitly put into the Public Domain. zlib Zlib (BSD-like) license. http://www.zlib.net/zlib_license.html If a package has components covered by different licenses (for example, GPL2 and the LGPL), use the <license> subdirectory for the more restrictive license. If a package allows the choice of a license to use, we'll generally use the less restrictive license. If in doubt about where a package should be located, please contact <core@NetBSD.org> for advice. Migration Strategy: Eventually src/dist (and associated framework in other base source directories) and src/gnu will be migrated to this hierarchy. Maintenance Strategy: The sources under src/external/<license>/<package>/dist/ are generally a combination of a published distribution plus changes that we submit to the maintainers and that are not yet published by them. Make sure all changes made to the external sources are submitted to the appropriate maintainer, but only after coordinating with the NetBSD maintainers.