Date: Mon, 17 Jul 2023 09:05:51 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Nuno Teixeira <eduardo@freebsd.org> Cc: Daniel Engberg <diizzy@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: <ZLUEbyybuQ1Qd9oK@FreeBSD.org> In-Reply-To: <CAFDf7U%2BC1oZWKZ=eeK-Wwt1G0it2pUE8%2BLOokaZB0c3YNGTD7g@mail.gmail.com> References: <202307162022.36GKMrdt060736@gitrepo.freebsd.org> <CAFDf7U%2BC1oZWKZ=eeK-Wwt1G0it2pUE8%2BLOokaZB0c3YNGTD7g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZLUEbyybuQ1Qd9oK>