From nobody Sun Oct 30 23:51:14 2022 X-Original-To: dev-commits-ports-main@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4N0tN56sFGz4gxnn; Sun, 30 Oct 2022 23:51:17 +0000 (UTC) (envelope-from diizzy@FreeBSD.org) Received: from relay7-d.mail.gandi.net (relay7-d.mail.gandi.net [217.70.183.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4N0tN5305Pz3FbF; Sun, 30 Oct 2022 23:51:17 +0000 (UTC) (envelope-from diizzy@FreeBSD.org) Received: (Authenticated sender: daniel.engberg@pyret.net) by mail.gandi.net (Postfix) with ESMTPA id 80D0020003; Sun, 30 Oct 2022 23:51:14 +0000 (UTC) List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-main@freebsd.org X-BeenThere: dev-commits-ports-main@freebsd.org MIME-Version: 1.0 Date: Mon, 31 Oct 2022 00:51:14 +0100 From: Daniel Engberg To: Yuri Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org, Thierry Subject: Re: git: b095fb085850 - main - security/amavisd-new: Use USE_GITLAB In-Reply-To: References: <202210302006.29UK6a96011531@gitrepo.freebsd.org> <47d5123e-f2a0-be5b-020f-4f4c28e1d1c5@tsoft.com> Message-ID: X-Sender: diizzy@FreeBSD.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Rspamd-Queue-Id: 4N0tN5305Pz3FbF X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 2022-10-30 22:25, Yuri wrote: > On 10/30/22 14:05, Thierry Thomas wrote: >> Yes, portscout does not know how to track commit hashes. >> >> In these cases, I suggest to use some RSS reader: e.g. on the page >> there is an icon "Tags >> feed" >> which should be >> usuable from any RSS reader. >> >> Another good mean is Repology (by Dmitry Marakasov / amdmi3): >> . Once subscribed as a >> maintainer, you can get a notifications feed. > > > One in-tree solution would be to enhance USE_GITLAB to be able to set > version-based MASTER_SITES URL for GitLab projects. > > > Until such improvement happens I suggest that Daniel reverts this and > similar changes since they really degrade functionality and don't add > any benefit. > > > > Yuri It's in the works and we preferably want to align the very few ports left that doesn't already use USE_GITLAB for consistency and upcoming exp-run. I've shared more details in PR 267104 about it. I agree it's not ideal however I would still argue that it's better than having a few ports working around the framework when we do have functionality in place and working on improving it. As Thierry pointed out there are good alternatives to Portscout in edge cases which several committers already use. Best regard, Daniel