Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Oct 2001 09:36:18 -0400
From:      Yarema <yds@dppl.com>
To:        courier-users@lists.sourceforge.net, ports@FreeBSD.org
Cc:        Neil Blakey-Milner <nbm@mithrandr.moria.org>, Sam Varshavchik <mrsam@courier-mta.com>
Subject:   Re: Courier-MTA on FreeBSD
Message-ID:  <668830000.1003930578@volyn.dppl.net>

next in thread | raw e-mail | index | archive | help
Well I finally submitted Courier-MTA to FreeBSD ports.
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31473 and sysconftool 
http://www.freebsd.org/cgi/query-pr.cgi?pr=31475 on which the courier build 
depends.

install/deinstall/reinstall/package/pkg_delete/pkg_add all seem to work. 
Optional BUILD_DEPENDS include expect, gpg, [ai]spell and procmail.  The 
package does not have a RUN_DEPENDS on the above since it is my 
understanding that removing the above packages will not break a running 
Courier system.  In my oppinion installing Courier should not cause a 
dependency chain reaction of expect->tcl->tk->X11.  The BUILD_DEPENDS is 
only there so Courier's configure can figure out the right paths.  Patching 
the autoconf files with paths more more likely to be correct on FreeBSD 
broke configure.  So a BUILD_DEPENDS seemed like a cleaner approach.

One such implicit dependency I noticed but don't have a fix for yet is when 
building --with-authldap and OpenLDAP2 is built with Berkeley DB3.  This 
causes most courier binaries to be linked with db3.so although the *.dat 
files created by courier are still Berkeley DB 1.85 style.  Everything 
still works it just doesn't seem right to me.  Perhaps if the autoconf 
files were modified to look for dbopen in libc before they ever look at 
libdb or libdb3 this might be solved.  Then again maybe not.  In any case I 
believe that all *BSD distributions have included Berkeley DB 1.85 in libc 
for years.

I'm thinking of splitting the port into master/slave ports where the slave 
ports would only build/install authdaemond.{ldap,mysql,pgsql} plus related 
config and support files.  This would for the most part solve the above db3 
linking issue.

I switched one of my production servers to courier and everything seems to 
work fine.  Fortunatley there's no file conflicts between postfix and 
courier.  I had to fall back to postfix on my first attempt since courier 
wouldn't resolve any DNS.  Rebuilding courier --without-ipv6 solved that 
problem.  I only use djbdns and not BIND.  So for what it's worth courier 
--with-ipv6 does not work with djbdns.

-- 
Yarema

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?668830000.1003930578>