From owner-freebsd-ports@freebsd.org Sat Mar 27 11:42:12 2021 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ADD175C14C3 for ; Sat, 27 Mar 2021 11:42:12 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F6xlR5MVBz3MbG for ; Sat, 27 Mar 2021 11:42:11 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4F6xlJ0fdrz6fPH; Sat, 27 Mar 2021 12:42:04 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id 73YHK6ak_f6A; Sat, 27 Mar 2021 12:42:01 +0100 (CET) Subject: Re: Python 2.7 removal outline To: Anatoly , freebsd-ports@freebsd.org References: <20210324130347.GA29020@freefall.freebsd.org> <20210327124436.2fdd99b5@asd2.localdomain> From: Guido Falsi Message-ID: <4483a58c-9f16-e7fc-7742-5dfa23485e43@madpilot.net> Date: Sat, 27 Mar 2021 12:42:00 +0100 In-Reply-To: <20210327124436.2fdd99b5@asd2.localdomain> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4F6xlR5MVBz3MbG X-Spamd-Bar: - X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[159.69.1.99:from]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MISSING_MIME_VERSION(2.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[159.69.1.99:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; NEURAL_HAM_SHORT(-1.00)[-0.995]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-ports] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Mar 2021 11:42:12 -0000 On 27/03/21 10:44, Anatoly wrote: > On Thu, 25 Mar 2021 23:06:27 -0700 > Chris wrote: > >> On 2021-03-25 22:24, Kurt Jaeger wrote: > >>> The portmgr@ role is a huge task and all the reasons (limited time, >>> dayjobs, etc) ares valid for those folks from portmgr as for >>> the rest of the ports maintainers and committers. >> Indeed, and don't think that hadn't occurred to me. In fact I >> suspected that portmgr@ was feeling a bit overwhelmed, and that >> *that* triggered the seemingly overreaching python announcement. >> May I humbly request a petition for such large-sweeping changes? IMHO >> this will give portmgr@ the opportunity to get caught up, and perhaps >> get some assistance -- maybe we all come up with an idea that saves >> _everyones_ bacon. :-) > > I already miss tools depending on gtk1.2, qt3, qt4 in ports. > Maybe it makes sense to introduce new "flag" > NOAUTOBUILD= > To mark the ports from which no packages should be build > quarterly automatically to reduce portmgr@ load, instead of just > dropping those ports out of ports tree? And leave all the care of those > ports to their maintainers, requiring them some kind of "pings" to > detect if maintainer is "alive" as the only criteria to keep port in > the tree? > If I understand what you propose you also mean that updates to the ports tree infrastructure and to ports not marked "NOAUTOBUILD" don't need to care if the NOAUTOBUILD ports get broken in the process. If that is so, you can already do this. Just create a repo on github with a port overlay, or fork the ports tree git repo (just wait a few days for the migration of the official ports tree to git) and you can add all the ports for old software you need and maintain them, or find other people to help you doing it. If you find the resources you can also provide CI and binary packages for them. There iss no need for the project's or portmgr involvement. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > -- Guido Falsi