From owner-freebsd-ports@freebsd.org Sat Mar 27 09:44:00 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 511705BEC80 for ; Sat, 27 Mar 2021 09:44:00 +0000 (UTC) (envelope-from anatoly@kazanfieldhockey.ru) Received: from kazanfieldhockey.ru (kazanfieldhockey.ru [78.138.152.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "kazanfieldhockey.ru", Issuer "System Administrator" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F6v732SCLz3Df6 for ; Sat, 27 Mar 2021 09:43:59 +0000 (UTC) (envelope-from anatoly@kazanfieldhockey.ru) Received: from asd2.localdomain (host-175-22.static.telecet.ru [87.117.175.22]) (authenticated bits=0) by kazanfieldhockey.ru (8.15.2/8.15.2) with ESMTPSA id 12R9BPH0048546 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 27 Mar 2021 12:11:27 +0300 (MSK) (envelope-from anatoly@kazanfieldhockey.ru) Date: Sat, 27 Mar 2021 12:44:36 +0300 From: Anatoly To: freebsd-ports@freebsd.org Subject: Re: Python 2.7 removal outline Message-ID: <20210327124436.2fdd99b5@asd2.localdomain> In-Reply-To: References: <20210324130347.GA29020@freefall.freebsd.org> X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd12.2) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (kazanfieldhockey.ru [192.168.13.2]); Sat, 27 Mar 2021 12:11:27 +0300 (MSK) X-Rspamd-Queue-Id: 4F6v732SCLz3Df6 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of anatoly@kazanfieldhockey.ru has no SPF policy when checking 78.138.152.250) smtp.mailfrom=anatoly@kazanfieldhockey.ru X-Spamd-Result: default: False [-0.87 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[78.138.152.250:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[78.138.152.250:from:127.0.2.255]; DMARC_NA(0.00)[kazanfieldhockey.ru]; NEURAL_SPAM_SHORT(0.23)[0.233]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:28840, ipnet:78.138.144.0/20, country:RU]; RCVD_COUNT_TWO(0.00)[2]; 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 09:44:00 -0000 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?