From nobody Mon Jul 17 16:32:34 2023 X-Original-To: dev-commits-ports-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4R4SKz5S8dz4mttt; Mon, 17 Jul 2023 16:32:39 +0000 (UTC) (envelope-from diizzy@FreeBSD.org) Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [IPv6:2001:4b98:dc4:8::228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4R4SKz0X3hz4Cxr; Mon, 17 Jul 2023 16:32:38 +0000 (UTC) (envelope-from diizzy@FreeBSD.org) Authentication-Results: mx1.freebsd.org; none Received: by mail.gandi.net (Postfix) with ESMTPA id E8C761BF209; Mon, 17 Jul 2023 16:32:34 +0000 (UTC) List-Id: Commit messages for all branches of the ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-all@freebsd.org X-BeenThere: dev-commits-ports-all@freebsd.org MIME-Version: 1.0 Date: Mon, 17 Jul 2023 18:32:34 +0200 From: Daniel Engberg To: Alexey Dokuchaev Cc: Nuno Teixeira , ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 4dd1ae7e79b4 - main - www/awffull: Deprecate and set expiration date to 2023-09-30 In-Reply-To: References: <202307162022.36GKMrdt060736@gitrepo.freebsd.org> Message-ID: <07f8bb9101a96df4289b12bb94cbd282@FreeBSD.org> X-Sender: diizzy@FreeBSD.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-GND-Sasl: daniel.engberg@pyret.net X-Rspamd-Queue-Id: 4R4SKz0X3hz4Cxr X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29169, ipnet:2001:4b98::/32, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 2023-07-17 11:05, Alexey Dokuchaev wrote: > On Sun, Jul 16, 2023 at 10:16:57PM +0100, Nuno Teixeira wrote: >> Hello Daniel, >> >> Is there any policy to protect "classic" ports from deletion? >> >> games/cursive is a good example with no upstream alive, just an >> archive. >> I believe that there is more examples that follow this situation. > > This topic is brought up from time to time; I'm also against removing > non-broken (buildable, working) ports, but the official position seems > to be "Ports Collection is not a software museum". :-/ > > If you enjoy some particular abandonware port(s), the best way to > prevent > their removal is to take maintainership (so if they break, pkg-fallout@ > will notify you) and use them on the regular basis (so it they build, > but > stop working, you'd also know quickly). > > ./danfe Hi, I do try to do some evaulation before deprecating ports. * Is upstream still active or at least was somewhat recently? * Fetchable? * Keeps up with todays standards/good practice? * Maintained and/or at least historically maintained within a reasonable of time? By that I mean proactive maintenance not drive-by/last minute fixes. * Do we have alternatives in tree? If there's a maintainer a PR is submitted and the regular 2 weeks timeout applies before any changes are committed. Best regards, Daniel