Date: Tue, 2 Jul 2019 13:53:43 +0000 From: Mark Linimon <linimon@lonesome.com> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: Baptiste Daroussin <bapt@freebsd.org>, Piotr Kubaj <pkubaj@anongoth.pl>, Greg Lewis <glewis@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r505640 - head/java/openjdk11 Message-ID: <20190702135343.GB17473@lonesome.com> In-Reply-To: <20190702104415.GB59302@FreeBSD.org> References: <201907012118.x61LIIQr011692@repo.freebsd.org> <20190702072450.GA17073@KGPE-D16> <20190702082607.GA45590@FreeBSD.org> <20190702083515.seykaqqjd77zyyr2@ivaldir.net> <20190702104415.GB59302@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 02, 2019 at 10:44:15AM +0000, Alexey Dokuchaev wrote:
> Right; unfortunately, often people who commit these changes do not
> bother to check with the actual code to see if a different/better
> solution is available (or even in order).
Sigh.
Yes, I'm sure that I could first do tests with c89, then whatever failed,
try again with c99, then try c11, then try again with c++11-lang, then ...
etc. etc.
Or I could carefully read the code of each port I'm trying to fix.
OTOH I would like to have powerpc64 ports usable before FreeBSD-19
comes out.
fwiw the stats on built packages:
Mon Nov 19 13:48:26 UTC 2018 16485
Sun Jun 16 06:10:04 UTC 2019 27953
I'm not even going to try to look up the number of build tests and
commits involved in getting us to this point. Hint: the former is
not the hundreds, it's in the thousands.
mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190702135343.GB17473>