Fix default ssl certs path for the mk*cert tools so that it works out

of the box.
While here, fix REVISION to deal with multi packages.

ok giovanni@ (maintainer)
This commit is contained in:
ajacoutot 2012-04-10 22:31:10 +00:00
parent 86813762f1
commit 5c6d2f6893
2 changed files with 6 additions and 4 deletions

View File

@ -1,15 +1,17 @@
# $OpenBSD: Makefile,v 1.81 2012/03/08 12:13:00 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.82 2012/04/10 22:31:10 ajacoutot Exp $
COMMENT-main= imap server for maildir format mailboxes
COMMENT-pop3= pop3 server for maildir format mailboxes
V= 4.10.0
REVISION= 1
DISTNAME= courier-imap-${V}
PKGNAME-main= ${DISTNAME}
FULLPKGNAME-pop3= courier-pop3-${V}
FULLPKGPATH-pop3= mail/courier-imap,-pop3
REVISION-main= 2
REVISION-pop3= 1
CATEGORIES= mail
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=courier/}
@ -60,7 +62,7 @@ CONFIGURE_ARGS= --sbindir=${PREFIX}/sbin \
--with-piddir=${COURIERSTATE} \
--with-makedatprog \
--with-db=gdbm \
--with-certsdir=/etc/ssl/private \
--with-certsdir=/etc/ssl \
--cache-file=${WRKDIR}/courier-imap.cache
CONFIGURE_ENV+= OPENSSL=/usr/sbin/openssl

View File

@ -5,4 +5,4 @@ Pay particular attention to the details in imapd.cnf, and read ssl(8) if
necessary. You MUST set the CN in imapd.cnf to the hostname by which
your IMAP server is accessed, or else clients will complain. When this
is done, you can use the 'mkimapdcert' script to automatically generate
a server certificate, which is installed into /etc/ssl/private/imapd.pem
a server certificate, which is installed into /etc/ssl/imapd.pem