Date: Wed, 1 Jan 2020 21:46:13 +0100 From: Franco Fichtner <franco@lastsummer.de> To: "@lbutlr" <kremels@kreme.com> Cc: FreeBSD <freebsd-ports@freebsd.org> Subject: Re: Portmaster failing Message-ID: <A8202C42-7EE5-4235-874A-D5D8C63E2413@lastsummer.de> In-Reply-To: <D4A3ED2A-A208-44DD-876B-5CF3F8EE3541@kreme.com> References: <8DDB987C-5276-4F35-BBD1-84043ED26E03@kreme.com> <E974C7FA-68A2-4B3F-B230-0DDF46AEEE4C@lastsummer.de> <D4A3ED2A-A208-44DD-876B-5CF3F8EE3541@kreme.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 1. Jan 2020, at 9:42 PM, @lbutlr <kremels@kreme.com> wrote: >=20 > On 01 Jan 2020, at 13:40, Franco Fichtner <franco@lastsummer.de> = wrote: >> security/openssl was removed before, now security/openssl111 has = become security/openssl. >=20 > Ugh. >=20 >> A bit too eager for my taste, but that's why we all have private = trees, don't we. ;) >=20 > This is going to go poorly, if previous attempts to update to 1.1 are = any indication. With PHP 5.6 axed prematurely a while back I am interested to see = OpenSSL 1.0.2 phased out now with a number of ports still not supporting 1.1.1 and = seeing them marked as broken sooner or later. With all this in mind, I'm surprised Python did not suffer the same fate and was deprecate-extended to the end of 2020 in the ports tree which is = an unusual 180 regarding previous arguments that having expired ports still supported is "too much work". Happy new year, Franco
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A8202C42-7EE5-4235-874A-D5D8C63E2413>