[pkg-kolab] r200 - trunk/kolab-cyrus-imapd/debian

Steffen Joeris white-guest at costa.debian.org
Tue Jan 24 11:50:14 UTC 2006


Author: white-guest
Date: 2006-01-24 11:50:13 +0000 (Tue, 24 Jan 2006)
New Revision: 200

Removed:
   trunk/kolab-cyrus-imapd/debian/imap.pam
   trunk/kolab-cyrus-imapd/debian/lmtp.pam
   trunk/kolab-cyrus-imapd/debian/mupdate.pam
   trunk/kolab-cyrus-imapd/debian/pop.pam
   trunk/kolab-cyrus-imapd/debian/sieve.pam
Modified:
   trunk/kolab-cyrus-imapd/debian/rules
Log:
* we don't use pam
* we use saslauthd and directly ldap, so no need for pam


Deleted: trunk/kolab-cyrus-imapd/debian/imap.pam
===================================================================
--- trunk/kolab-cyrus-imapd/debian/imap.pam	2006-01-24 11:47:35 UTC (rev 199)
+++ trunk/kolab-cyrus-imapd/debian/imap.pam	2006-01-24 11:50:13 UTC (rev 200)
@@ -1,14 +0,0 @@
-# PAM configuration file for Cyrus IMAP service
-# $Id: imap.pam 5 2005-03-12 23:19:45Z sven $
-#
-# If you want to use Cyrus in a setup where users don't have
-# accounts on the local machine, you'll need to make sure
-# you use something like pam_permit for account checking.
-#
-# Remember that SASL (and therefore Cyrus) accesses PAM 
-# modules through saslauthd, and that SASL can only deal with
-# plaintext passwords if PAM is used.
-#
-
- at include common-auth
- at include common-account

Deleted: trunk/kolab-cyrus-imapd/debian/lmtp.pam
===================================================================
--- trunk/kolab-cyrus-imapd/debian/lmtp.pam	2006-01-24 11:47:35 UTC (rev 199)
+++ trunk/kolab-cyrus-imapd/debian/lmtp.pam	2006-01-24 11:50:13 UTC (rev 200)
@@ -1,14 +0,0 @@
-# PAM configuration file for Cyrus LMTP service
-# $Id: lmtp.pam 5 2005-03-12 23:19:45Z sven $
-#
-# If you want to use Cyrus in a setup where users don't have
-# accounts on the local machine, you'll need to make sure
-# you use something like pam_permit for account checking.
-#
-# Remember that SASL (and therefore Cyrus) accesses PAM 
-# modules through saslauthd, and that SASL can only deal with
-# plaintext passwords if PAM is used.
-#
-
- at include common-auth
- at include common-account

Deleted: trunk/kolab-cyrus-imapd/debian/mupdate.pam
===================================================================
--- trunk/kolab-cyrus-imapd/debian/mupdate.pam	2006-01-24 11:47:35 UTC (rev 199)
+++ trunk/kolab-cyrus-imapd/debian/mupdate.pam	2006-01-24 11:50:13 UTC (rev 200)
@@ -1,14 +0,0 @@
-# PAM configuration file for Cyrus Murder mupdate service
-# $Id: mupdate.pam 5 2005-03-12 23:19:45Z sven $
-#
-# If you want to use Cyrus in a setup where users don't have
-# accounts on the local machine, you'll need to make sure
-# you use something like pam_permit for account checking.
-#
-# Remember that SASL (and therefore Cyrus) accesses PAM 
-# modules through saslauthd, and that SASL can only deal with
-# plaintext passwords if PAM is used.
-#
-
- at include common-auth
- at include common-account

Deleted: trunk/kolab-cyrus-imapd/debian/pop.pam
===================================================================
--- trunk/kolab-cyrus-imapd/debian/pop.pam	2006-01-24 11:47:35 UTC (rev 199)
+++ trunk/kolab-cyrus-imapd/debian/pop.pam	2006-01-24 11:50:13 UTC (rev 200)
@@ -1,14 +0,0 @@
-# PAM configuration file for Cyrus POP3 service
-# $Id: pop.pam 5 2005-03-12 23:19:45Z sven $
-#
-# If you want to use Cyrus in a setup where users don't have
-# accounts on the local machine, you'll need to make sure
-# you use something like pam_permit for account checking.
-#
-# Remember that SASL (and therefore Cyrus) accesses PAM 
-# modules through saslauthd, and that SASL can only deal with
-# plaintext passwords if PAM is used.
-#
-
- at include common-auth
- at include common-account

Modified: trunk/kolab-cyrus-imapd/debian/rules
===================================================================
--- trunk/kolab-cyrus-imapd/debian/rules	2006-01-24 11:47:35 UTC (rev 199)
+++ trunk/kolab-cyrus-imapd/debian/rules	2006-01-24 11:50:13 UTC (rev 200)
@@ -191,12 +191,9 @@
 	#mv $(TMPPKG)/lib/* $(TMPPKG)/usr/lib
 
 	# for stuff in /etc
-	mkdir -p $(TMPPKG)/etc/cyrus $(TMPPKG)/etc/pam.d
+	mkdir -p $(TMPPKG)/etc/cyrus
 	install -m 644 debian/imapd.conf    $(TMPPKG)/etc
 	install -m 644 debian/cyrus.conf    $(TMPPKG)/etc
-	(cd debian ; for i in *.pam ;\
-		do install -m 644 $$i $(TMPPKG)/etc/pam.d/$${i%.pam} ;\
-	done)
 
 	# We rename some utils, so we need to sort out the manpages
 	for i in master reconstruct quota deliver ; do \
@@ -279,7 +276,6 @@
 	dh_installexamples -p kolab-cyrus-admin
 	dh_installmenu -i
 #	dh_installlogrotate -i
-#	dh_installpam -i
 #	dh_installmime -i
 #	dh_installcron -i
 	dh_installman -i
@@ -304,7 +300,6 @@
 	dh_installexamples -p $(MAINPKG) -p kolab-libcyrus-imap-perl -p kolab-cyrus-clients
 	dh_installmenu -a
 #	dh_installlogrotate -a
-#	dh_installpam -a
 #	dh_installmime -a
 	dh_installinit -p $(MAINPKG) --noscripts --name=kolab-cyrus
 	dh_installcron -a

Deleted: trunk/kolab-cyrus-imapd/debian/sieve.pam
===================================================================
--- trunk/kolab-cyrus-imapd/debian/sieve.pam	2006-01-24 11:47:35 UTC (rev 199)
+++ trunk/kolab-cyrus-imapd/debian/sieve.pam	2006-01-24 11:50:13 UTC (rev 200)
@@ -1,14 +0,0 @@
-# PAM configuration file for Cyrus SIEVE timsieved service
-# $Id: sieve.pam 5 2005-03-12 23:19:45Z sven $
-#
-# If you want to use Cyrus in a setup where users don't have
-# accounts on the local machine, you'll need to make sure
-# you use something like pam_permit for account checking.
-#
-# Remember that SASL (and therefore Cyrus) accesses PAM 
-# modules through saslauthd, and that SASL can only deal with
-# plaintext passwords if PAM is used.
-#
-
- at include common-auth
- at include common-account




More information about the pkg-kolab-devel mailing list