Date: Sun, 30 Nov 2003 17:00:49 -0500 From: Richard Coleman <richardcoleman@mindspring.com> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: Andreas Klemm <andreas@FreeBSD.org> Subject: Re: 5.2-BETA and related ports issues Message-ID: <3FCA6891.1020400@mindspring.com> In-Reply-To: <xzpbrqtepp5.fsf@dwp.des.no> References: <200311281553.hASFrURT003309@siralan.org> <20031130084800.GA64364@titan.klemm.apsfilter.org> <3FCA12B3.7070604@mindspring.com> <200311301746.27134.freebsd-current@webteckies.org> <xzpbrqtepp5.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote: > Melvyn Sopacua <freebsd-current@webteckies.org> writes: > >>Then you can just as easily nuke the entire mailer.conf principle and symlink >>bin/postfix to etc/rc.d/050.postfix.sh. > > > This is actually one of the two recommended ways of starting postfix > (and the one I prefer). The main reason for mailer.conf to exist is > that a lot of scripts have /usr/sbin/sendmail hardcoded and TPTB > decided that they didn't want to use 'use.perl port'-style symlinks. > > DES But all these seem like such hacks. It would be so much cleaner to move sendmail.sh out of the way and just add postfix.sh to /etc/rc.d, rather than using tricks with symlinks and rc.conf variables. If you have a small number of ports added, it's not a big deal. But all these hacks get confusing when you have a lot of ports, each doing it's own special trick. The mailer.conf issue (for mail injection) is a separate issue and there's really no way around that. Richard Coleman richardcoleman@mindspring.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FCA6891.1020400>