[csw-devel] SF.net SVN: gar:[16684] csw/mgar/pkg/sasl/trunk
guengel at users.sourceforge.net
guengel at users.sourceforge.net
Wed Jan 4 21:32:59 CET 2012
Revision: 16684
http://gar.svn.sourceforge.net/gar/?rev=16684&view=rev
Author: guengel
Date: 2012-01-04 20:32:59 +0000 (Wed, 04 Jan 2012)
Log Message:
-----------
sasl/trunk: Added changelog.CSW. CSWsaslauthd now prints postmsg. sasldb2 password file will be migrate to /etc/opt/csw. READMEs improved.
Modified Paths:
--------------
csw/mgar/pkg/sasl/trunk/Makefile
csw/mgar/pkg/sasl/trunk/files/README.sasl
csw/mgar/pkg/sasl/trunk/files/README.saslauthd
Added Paths:
-----------
csw/mgar/pkg/sasl/trunk/files/CSWsaslauthd.postmsg
csw/mgar/pkg/sasl/trunk/files/changelog.CSW
Modified: csw/mgar/pkg/sasl/trunk/Makefile
===================================================================
--- csw/mgar/pkg/sasl/trunk/Makefile 2012-01-04 18:37:15 UTC (rev 16683)
+++ csw/mgar/pkg/sasl/trunk/Makefile 2012-01-04 20:32:59 UTC (rev 16684)
@@ -21,7 +21,12 @@
DISTFILES += saslauthd.conf.CSW
DISTFILES += README.sasl
DISTFILES += README.saslauthd
+DISTFILES += changelog.CSW
+DISTFILES += CSWsaslauthd.postmsg
+EXPANDVARS = CSWsaslauthd.postmsg
+POSTMSG = $(docdir)/saslauthd/CSWsaslauthd.postmsg
+
# For some reason or another, plugins are installed in
# $(prefix)/lib/sasl2, regardless of what --with-plugindir is set
# to. This patch will make the install routine put the plugins to
@@ -59,6 +64,7 @@
PKGFILES_CSWsaslauthd += $(docdir)/saslauthd/LDAP_SASLAUTHD
PKGFILES_CSWsaslauthd += $(docdir)/saslauthd/README.saslauthd
PKGFILES_CSWsaslauthd += $(docdir)/saslauthd/README.CSW
+PKGFILES_CSWsaslauthd += $(docdir)/saslauthd/CSWsaslauthd.postmsg
PKGFILES_CSWsaslauthd += /var/opt/csw/saslauthd
PACKAGES += CSWsaslgssapi
@@ -126,8 +132,8 @@
EXTRA_BUILD_ENV = _REENTRANT=1
-EXTRA_INC = /opt/csw/include/gssapi
-EXTRA_INC += /opt/csw/include/mysql
+EXTRA_INC = $(includedir)/gssapi
+EXTRA_INC += $(includedir)/mysql
EXTRA_INC += /opt/csw/postgresql/include
# Do not use LD_OPTIONS as it breaks tests by using the installed libraries
@@ -189,7 +195,10 @@
max_cmd_line=65535
SED_USR_LOCAL= sed -e 's|/usr/local|/opt/csw|g'
-MIGRATECONF = saslauthd.conf sasldb2
+MIGRATE_FILES_CSWsasl = "sasldb2"
+MIGRATE_FILES_CSWsaslauthd = "saslauthd.conf"
+MIGRATE_SOURCE_DIR = /opt/csw/etc
+MIGRATE_DEST_DIR = $(sysconfdir)
PRESERVECONF = /etc/opt/csw/saslauthd.conf /etc/opt/csw/saslauthd.init
INITSMF = /etc/opt/csw/init.d/cswsaslauthd
@@ -206,10 +215,11 @@
post-install-modulated: install-doc fix-path-manpages install-sample
- ginstall -d $(DESTDIR)/etc/opt/csw/init.d/
- ginstall $(WORKDIR)/saslauthd.init.CSW $(DESTDIR)/etc/opt/csw/
- ginstall $(WORKDIR)/saslauthd.conf.CSW $(DESTDIR)/etc/opt/csw/
- ginstall $(WORKDIR)/cswsaslauthd.init $(DESTDIR)/etc/opt/csw/init.d/cswsaslauthd
+ ginstall -d $(DESTDIR)$(sysconfdir)/init.d/
+ ginstall $(WORKDIR)/saslauthd.init.CSW $(DESTDIR)$(sysconfdir)
+ ginstall $(WORKDIR)/saslauthd.conf.CSW $(DESTDIR)$(sysconfdir)
+ ginstall $(WORKDIR)/cswsaslauthd.init $(DESTDIR)$(sysconfdir)/init.d/cswsaslauthd
+ ginstall $(WORKDIR)/CSWsaslauthd.postmsg $(DESTDIR)$(docdir)/saslauthd/
@$(MAKECOOKIE)
# The names 'client' and 'server' are a little generic, so we change
Added: csw/mgar/pkg/sasl/trunk/files/CSWsaslauthd.postmsg
===================================================================
--- csw/mgar/pkg/sasl/trunk/files/CSWsaslauthd.postmsg (rev 0)
+++ csw/mgar/pkg/sasl/trunk/files/CSWsaslauthd.postmsg 2012-01-04 20:32:59 UTC (rev 16684)
@@ -0,0 +1,8 @@
+
+---
+
+Please adjust @sysconfdir@/saslauthd.init before starting saslauthd.
+
+See also @docdir@/saslauthd/README.CSW
+
+---
Modified: csw/mgar/pkg/sasl/trunk/files/README.sasl
===================================================================
--- csw/mgar/pkg/sasl/trunk/files/README.sasl 2012-01-04 18:37:15 UTC (rev 16683)
+++ csw/mgar/pkg/sasl/trunk/files/README.sasl 2012-01-04 20:32:59 UTC (rev 16684)
@@ -1,25 +1,8 @@
-List of changes in sasl-2.1.25
-- Included sasl-sample-client and sasl-sample-server to ease
- testing of sasl setup.
+sasl README
+-----------
-- SASL application configuration files (e.g. Sendmail.conf) go into
- /opt/csw/lib/sasl2 or /opt/csw/lib/64/sasl2 for 64-bit binaries.
+ * The location of `sasldb2' has been moved from /opt/csw/etc to
+ /etc/opt/csw.
-List of changes in sasl-2.1.22,REV=2007.06.10
-- upgraded sasl to version 2.1.22
-- runpath was not applied for libraries [#1566][#1637][#1934][#2268]
-
-List of changes in sasl-2.1.21,REV=2006.03.09
-- /opt/csw/etc/sasldb2 is a directory [#1393]
-- preinstall script is using PKG_INSTALL_ROOT variable instead of PKG_ROOT_DIR
-
-List of changes in sasl-2.1.21,REV=2005.09.07:
-- upgraded to version 2.1.21
-- included unsupported LOGIN SASL mechanism, because I received several
- requests for this mechanism. Some mail clients (e.g. MS Outlook) only support
- LOGIN mechanism.
-- included auxprop plugins for MySQL, PostreSQL and SQLLite
-- included kerberos mechanisms (GSSAPI)
-- CSWsasl creates a group 'sasl'. Any process which is not running as root,
- must belong to this group to perform authentiaction against SASLdb or via saslauthd.
-
+ * SASL application configuration files (e.g. Sendmail.conf) go into
+ /opt/csw/lib/sasl2 or /opt/csw/lib/64/sasl2 for 64-bit binaries.
Modified: csw/mgar/pkg/sasl/trunk/files/README.saslauthd
===================================================================
--- csw/mgar/pkg/sasl/trunk/files/README.saslauthd 2012-01-04 18:37:15 UTC (rev 16683)
+++ csw/mgar/pkg/sasl/trunk/files/README.saslauthd 2012-01-04 20:32:59 UTC (rev 16684)
@@ -1,26 +1,21 @@
-Configuration file for saslauthd init/smf script is in /etc/opt/csw/saslauthd.init
-Configuration file for saslauthd is in /etc/opt/csw/saslauthd.conf
+saslauthd README
+----------------
-Details concerning /etc/opt/csw/saslauthd.conf can be found in
-/opt/csw/share/doc/saslauthd/LDAP_SASLAUTHD
+The configuration file for the saslauthd startup script is
-If you experience memory leak with PAM mechanism, then try to disable
-worker processes with -n 0. It may affect performance, because
-saslauthd will spawn a new process for each authentication.
+ /etc/opt/csw/saslauthd.init
+Please note, that prior starting the saslauthd daemon, you have to set
+a mechanism this file, or the saslauthd daemon won't start.
-List of changes in saslauthd-2.1.22,REV=2007.06.10
-- sasl updated to 2.1.22
-- sasl was built with invalid list of search directories for libraries [#2103]
-- man page was in postscript format [#2261]
+The Configuration file for saslauthd daemon is located in
+ /etc/opt/csw/saslauthd.conf
-List of changes in saslauthd-2.1.21,REV=2006.03.09:
-- Communication with SASL is done with unix sockets because ipc doors mechanism is unreliable [#1222] [#1225] [#1227]
-- Authentification mechanism should be configureable without editing init.d script [#1221]
-- postinstall script is using PKG_INSTALL_ROOT variable instead of PKG_ROOT_DIR
+You may change this by ajdusting /etc/opt/csw/saslauth.init. Details
+concerning /etc/opt/csw/saslauthd.conf can be found in
+/opt/csw/share/doc/saslauthd/LDAP_SASLAUTHD
-
-List of changes in saslauthd-2.1.21,REV=2005.09.07:
-- updated to Cyrus SASL 2.1.21
-- /etc/init.d/CSWsaslauthd renamed to /etc/init.d/cswsaslauthd to be consistent with other blastwave packages
+If you experience memory leak with PAM mechanism, then try to disable
+worker processes with -n 0. It may affect performance, because
+saslauthd will spawn a new process for each authentication.
Added: csw/mgar/pkg/sasl/trunk/files/changelog.CSW
===================================================================
--- csw/mgar/pkg/sasl/trunk/files/changelog.CSW (rev 0)
+++ csw/mgar/pkg/sasl/trunk/files/changelog.CSW 2012-01-04 20:32:59 UTC (rev 16684)
@@ -0,0 +1,70 @@
+sasl (2.1.25,REV=2012.01.04)
+
+ * README.sasl, README.saslauthd: moved changelog entries to
+ changelog.csw.
+
+ * README.saslauthd: improved documentation.
+
+ * sasldb2: file will be migrated from /opt/csw/etc/ to /etc/opt/csw.
+
+ -- Rafael Ostertag <raos at opencsw.org> Wed, 04 Jan 2012 19:41:27 +0100
+
+
+sasl (2.1.25,REV=2011.11.06)
+
+ * Included pluginviewer, sasl-sample-client, and sasl-sample-server
+ to ease testing of sasl setup.
+
+ * SASL application configuration files (e.g. Sendmail.conf) go into
+ /opt/csw/lib/sasl2 or /opt/csw/lib/64/sasl2 for 64-bit binaries.
+
+ -- Rafael Ostertag <raos at opencsw.org> Wed, 04 Jan 2012 19:41:27 +0100
+
+
+sasl (2.1.22,REV=2007.06.10)
+
+ * sasl updated to 2.1.22
+
+ * runpath was not applied for libraries [#1566][#1637][#1934][#2268]
+
+ * saslauthd: sasl was built with invalid list of search directories for
+ libraries [#2103]
+
+ * saslauthd: man page was in postscript format [#2261]
+
+
+sasl (2.1.21,REV=2006.03.09)
+
+ * /opt/csw/etc/sasldb2 is a directory [#1393]
+
+ * preinstall script is using PKG_INSTALL_ROOT variable instead of
+ PKG_ROOT_DIR
+
+ * saslauthd: Communication with SASL is done with unix sockets because ipc
+ doors mechanism is unreliable [#1222] [#1225] [#1227]
+
+ * sasluthd: Authentification mechanism should be configureable without editing
+ init.d script [#1221]
+
+ * saslauthd: postinstall script is using PKG_INSTALL_ROOT variable instead of
+ PKG_ROOT_DIR
+
+
+sasl (2.1.21,REV=2005.09.07)
+
+ * upgraded to version 2.1.21
+
+ * included unsupported LOGIN SASL mechanism, because I received
+ several requests for this mechanism. Some mail clients (e.g. MS
+ Outlook) only support LOGIN mechanism.
+
+ * included auxprop plugins for MySQL, PostreSQL and SQLLite
+
+ * included kerberos mechanisms (GSSAPI)
+
+ * CSWsasl creates a group 'sasl'. Any process which is not running
+ as root, must belong to this group to perform authentiaction
+ against SASLdb or via saslauthd.
+
+ * saslauthd: /etc/init.d/CSWsaslauthd renamed to /etc/init.d/cswsaslauthd to be
+ consistent with other blastwave packages
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
More information about the devel
mailing list