Date: Sat, 12 Oct 2013 02:37:12 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: svn-ports-head@freebsd.org, Alexey Dokuchaev <danfe@FreeBSD.org>, Baptiste Daroussin <bapt@FreeBSD.org>, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r327601 - head/Mk Message-ID: <alpine.LNX.2.00.1310120235240.2211@trevally.site> In-Reply-To: <523D7B20.6020908@FreeBSD.org> References: <201309190805.r8J855cW009011@svn.freebsd.org> <20130921023225.GA19307@FreeBSD.org> <20130921104936.GQ73535@ithaqua.etoilebsd.net> <523D7B20.6020908@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 21 Sep 2013, Bryan Drewery wrote: > We also plan to add more commit hooks for things that portlint has > checked for. Not everyone runs portlint, and portlint is essentially > unmaintained. It is currently severely lagging behind in feature-set > checking. By moving to ports, the feature-set checking is always > matching the tree. This is a bit confusing, and I think there are things portlint checks for that the ports infrastructure cannot? For example, a recent sweep to replace LAST_LINK by PKGNAMESUFFIX triggered new portlint warnings for me since PKGNAMESUFFIX was added at the wrong place. I thought we all are supposed to run portlint before commits? Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LNX.2.00.1310120235240.2211>