Date: Sat, 22 Dec 2018 23:50:25 +0100 From: Michael Grimm <trashcan@ellael.org> To: "freebsd-ports@freebsd.org" <freebsd-ports@FreeBSD.org> Subject: Re: security/clamav-milter fails to compile (preliminary patch included) Message-ID: <7CF7BC01-48FB-4BE5-8083-1D07B5381ADE@ellael.org> In-Reply-To: <20181223.073342.309673158694093354.yasu@utahime.org> References: <E3A96E14-75EE-4773-A24E-226B99F77540@ellael.org> <20181223.064839.1749206782508827440.yasu@utahime.org> <A71FB1C2-53E8-4043-AABC-F3FF234DB2CA@ellael.org> <20181223.073342.309673158694093354.yasu@utahime.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yasuhiro KIMURA <yasu@utahime.org> wrote: > Thank you for checking patch. Then I'll submit this patch to > Bugzilla. I may take for a while but will be committed to ports > repository. Thanks. "One more thing" ;-) Your patch will work, and thinking about the maturity of libmilter, your = patch will be an appropriate one. I am thinking about a more "future safe" solution for = security/clamav-milter: #) add an OPTION to security/clamav-milter's Makefile whether to = use libmilter from base or ports #) make the default to use port mail/libmilter #) because the latter will allow to automatically follow newest = developments of libmilter and clamav ports Don't get me wrong, you are the maintainer, thus, it is completely up to = you! Thanks again and kind regards, Michael=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7CF7BC01-48FB-4BE5-8083-1D07B5381ADE>