Date: Tue, 17 May 2011 07:22:14 -0400 From: Kevin Kobb <kkobb@skylinecorp.com> To: freebsd-ports@freebsd.org Subject: Re: Mailscanner update -- changes to the port Message-ID: <4DD25A66.2010900@skylinecorp.com> In-Reply-To: <BANLkTi=eizbZdDRjCCfxEMp5aeZ7NB_SkA@mail.gmail.com> References: <BANLkTi=eizbZdDRjCCfxEMp5aeZ7NB_SkA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/15/2011 6:38 AM, Chris Rees wrote: > Hi all, > > I've just finished working on the update for MailScanner, and I've > changed a few things that have annoyed me loads-- perhaps it's been > irritating for you too! > > > I've removed the extra targets for initial configuration etc, and > moved them into a pkg-install script, which means that it also does > the Right Thing when being installed from packages; no more messing > about doing manual moves of the million .sample files installed! > > Since I know loads of people rely on this port, please would people > try this out and let me know of any issues? Patch at [1] and shar at > [2]. > > Before people ask why I haven't done the usual method of putting lines > in pkg-plist for config files, take a look at how many there are... > > TIA, > > Chris > > [1] http://www.bayofrum.net/~crees/patches/mailscanner-4.83.5.patch > > [2] http://www.bayofrum.net/~crees/patches/mailscanner-4.83.5.shar > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" Did some quick testing on a non-production machine, and it seemed to work OK. Not so sure you need to get rid of the CHANGES.port file as I think it is more FreeBSD specific than just the upstream change log. However, it probably isn't a big deal either way. I'll keep working with it and let you know if I run across anything strange. Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DD25A66.2010900>