| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
packages. Convert LDAP-based applications to depend on openldap-client, and
bump PKGREVISION for those that depend on it by default.
|
|
|
|
Postfix snapshot 20051220 provides a plug-in architecture for SASL
authentication. With this, Postfix can support multiple SASL
implementations without source code patches.
Incompatibility with snapshot 20051220
======================================
The Postfix-with-Cyrus-SASL build procedure has changed. You now
need to specify -DUSE_CYRUS_SASL in addition to -DUSE_SASL_AUTH or
else you end up without any Cyrus SASL support. The error messages
are:
unsupported SASL server implementation: cyrus
unsupported SASL client implementation: cyrus
Major changes with snapshot 20051220
====================================
Plug-in support for SASL authentication in the SMTP server and in
the SMTP+LMTP client. With this, Postfix can support multiple SASL
implementations without source code patches. Some distributors may
even make SASL support a run-time linking option, just like they
do with Postfix lookup tables.
Hints and tips for plug-in developers are in the xsasl/README file.
For backwards compatibility the default plug-in type is Cyrus SASL,
so everything should behave like it did before. Some error messages
are slightly different, but these are generally improvements.
The "postconf -a" command shows what plug-in implementations are
available for the SMTP server, and "postconf -A" does the same for
the SMTP+LMTP client. Plug-in implementations are selected with
the smtpd_sasl_type, smtp_sasl_type and lmtp_sasl_type configuration
parameters.
Other new configuration parameters are smtpd_sasl_path, smtp_sasl_path
and lmtp_sasl_path. These are better left alone; they are introduced
for the convenience of other SASL implementations.
|
|
* lots of bug fixes and new features (see RELEASE_NOTES for details)
* sync PLIST.*, MESSAGE.*, Makefile and options.mk with pkgsrc/mail/postfix
|
|
PKGSRC_USE_TOOLS go away. There is now only a single USE_TOOLS variable
that specifies all of the tools we need to build/run the package.
|
|
|
|
tracked the Cyrus SASL 1.5.x releases, which are no longer maintained.
Adjust packages to use security/cyrus-sasl2 instead for SASL support.
This closes PR pkg/28218 and PR pkg/29736.
|
|
Ok'ed jlam@
|
|
so that we'd not force dependance on specific MySQL version, and instead pick
the currently installed mysql*-client (or install the default if there
is no mysql-client package installed yet)
this makes package buildable with arbitrary MySQL version, such as 3.23.x,
4.0.x or 4.1.x
|
|
which are the full option names used to set rpath directives for the
linker and the compiler, respectively. In places were we are invoking
the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is
inserted in case the flag is a word, e.g. -rpath. The default values
of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the
compiler that you use. They may be overridden on a ${OPSYS}-specific
basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG,
respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
|
|
into the bsd.options.mk framework. Instead of appending to
${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes
the default options to be the union of PKG_DEFAULT_OPTIONS and any
old USE_* and FOO_USE_* settings.
This fixes PR pkg/26590.
|
|
building STARTTLS support without IPv6.
|
|
Reduce the number of patches needed by Postfix by using the subst
framework and also by explicitly specifying more default values for
Postfix parameters. Also pass -I/usr/pkg/include/sasl to the compiler
when building using Cyrus SASLv2, which allows me to remove the patches
that added an unnecessary USE_SASL2_AUTH check.
|
|
This follows the example of the mail/dovecot package, as suggested by
<schmonz>.
|
