Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Jul 2023 18:32:34 +0200
From:      Daniel Engberg <diizzy@FreeBSD.org>
To:        Alexey Dokuchaev <danfe@freebsd.org>
Cc:        Nuno Teixeira <eduardo@freebsd.org>, 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
Message-ID:  <07f8bb9101a96df4289b12bb94cbd282@FreeBSD.org>
In-Reply-To: <ZLUEbyybuQ1Qd9oK@FreeBSD.org>
References:  <202307162022.36GKMrdt060736@gitrepo.freebsd.org> <CAFDf7U%2BC1oZWKZ=eeK-Wwt1G0it2pUE8%2BLOokaZB0c3YNGTD7g@mail.gmail.com> <ZLUEbyybuQ1Qd9oK@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07f8bb9101a96df4289b12bb94cbd282>