Date: Sun, 11 Apr 2021 11:54:51 +0200 From: Torsten Zuehlsdorff <freebsd@toco-domains.de> To: Tobias Kortkamp <tobik@freebsd.org>, Adriaan de Groot <adridg@freebsd.org> Cc: Gerald Pfeifer <gerald@pfeifer.com>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org, ale@freebsd.org Subject: Re: git: c6093a753e76 - main - databases/mysql55-server: fix check-plist Message-ID: <1f42d087-f259-c578-5934-1071909e0e7b@toco-domains.de> In-Reply-To: <YHK13C8X25px87/G@urd.tobik.me> References: <202104090946.1399kTCb092931@gitrepo.freebsd.org> <34dabf10-5e9b-37da-2d74-b4f38a357b2e@pfeifer.com> <2226559.mfXeX5GmMH@beastie.bionicmutton.org> <YHK13C8X25px87/G@urd.tobik.me>
index | next in thread | previous in thread | raw e-mail
On 11.04.21 10:39, Tobias Kortkamp wrote: > On Sun, Apr 11, 2021 at 01:10:17AM +0200, Adriaan de Groot wrote: >> No. Omitting the CMake argument changes the problem to "now there is an >> orphaned directory docs/". I suppose I *could* make it point somewhere that >> already exists, and then drop the post-install papering -- I'd prefer it if >> ale@ (maintainer, CC'ed) made that call, though: my primary concern is to deal >> simple with all the package-build failures that occur *before* upgrading >> CMake. > > Why do we still have MySQL 5.5? It has been EOL since December > 2018. Why should we continue to fix it? Shouldn't we put a > deprecation notice on the port now and let it expire? Same would be true for 5.7 since 2019: https://www.mysql.com/de/support/eol-notice.html (You need to search for "Support EOL for MySQL 5.7 on FreeBSD") And this would reduce it to 8.0? Which is quite a troublesome choice :D Best, Torstenhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1f42d087-f259-c578-5934-1071909e0e7b>