Date: Wed, 28 Feb 2024 13:38:19 -0800 From: Chris <portmaster@bsdforge.com> To: Florian Smeets <flo@freebsd.org> Cc: Miroslav Lachman <000.fbsd@quip.cz>, ports@freebsd.org Subject: Re: Proposed ports deprecation and removal policy Message-ID: <7d2a8e8e671578f99ed05431b68cf015@bsdforge.com> In-Reply-To: <1500d4f4-2bdb-4d3b-8848-900346f4d194@FreeBSD.org> References: <435edf7c-a956-4317-b327-3372de70dbef@FreeBSD.org> <fb42e7b5-be11-4d6f-bacd-90bfd361ed48@quip.cz> <1500d4f4-2bdb-4d3b-8848-900346f4d194@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2024-02-28 12:13, Florian Smeets wrote: > On 28.02.24 21:00, Miroslav Lachman wrote: >> On 28/02/2024 20:22, Florian Smeets wrote: >> >>> Ports can be removed immediately if one of the following conditions is >>> met: >>> >>> - Upstream distfile is no longer available from the original source/mirror >>> (Our and other distcaches e.g. Debian, Gentoo, etc do not count as >>> "available") >> >> I miss some sort of time frame like in the following cases. The way the >> sentence is written now, it looks like there may be an immediate removal on >> the first day of the outage. >> > > Good point. Yeah, it certainly isn't the intention to remove it immediately. > I > will make a note to add a time frame. I'm thinking 4 weeks, as that feels > long for > a site to go away and reappear, but we might just make it 3 months as with > most of > the other points. I'd vote for 3 (mos). But 2 also seems reasonable. So that those that use it. But don't update frequently get a chance to notice, and subsequently save/maintain it. :) > > Thanks > Florian -- --Chris Hutchinson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d2a8e8e671578f99ed05431b68cf015>