Date: Fri, 19 Nov 2021 23:44:57 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: Daniel Engberg <diizzy@FreeBSD.org>, "Mikhail T." <mi+ports@aldan.algebra.com> Cc: "freebsd-ports@FreeBSD.ORG" <freebsd-ports@freebsd.org> Subject: Re: Regarding port(s) you maintain in FreeBSD ports collection Message-ID: <6f098ce8-0361-543a-b480-83a147fa98a1@quip.cz> In-Reply-To: <9524a144672a383530187ed7369acea9@FreeBSD.org> References: <d8029a1dca2771ec0f7b9ca331488ea9@FreeBSD.org> <e0665090-7d17-c231-cafe-814bff599001@aldan.algebra.com> <a73b85b33a5e0b6ed61cb3e627165112@FreeBSD.org> <a1f15dbc-51e6-6ebd-5e57-14935da2f315@aldan.algebra.com> <9524a144672a383530187ed7369acea9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16/11/2021 22:46, Daniel Engberg wrote: > Hi Mikhail, > > There are numerous of reason why we need to remove ports, one major > reason is simply to have a sustainable repository. One example is the > deprecation of Python 2.x which is long overdue but we're slowly getting > there because there still are a few crucial pieces of software that > depends on it such as Chromium. What is sustainable repository? And why having "old" software in the ports tree makes it unsustainable? I am personally using software with latest release from 2009 and it still works, still is buildable on today's FreeBSD and is still useful. Why remove it? And with Python 2.7, Chromium and other ports, it is one of a few points where I really hate decision of portmgr team because some ports where immediately marked and expired and removed a year ago because of dependency on Python 2.7 but some (Chromium) are still there even if all of them use Python 2.7 for build. For example Iridium expired 2020-12-31, Falkon is marked expired 2021-06-23 but Chromium? Nothing, like it is not depending on the same Python 2.7. This disparity ****** me off. regards Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6f098ce8-0361-543a-b480-83a147fa98a1>