From owner-freebsd-ports@freebsd.org Wed Apr 28 18:03:25 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 27C855FC427 for ; Wed, 28 Apr 2021 18:03:25 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FVmhX50Lmz3CCb for ; Wed, 28 Apr 2021 18:03:24 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 13SI3Yqx015911 for ; Wed, 28 Apr 2021 11:03:42 -0700 (PDT) (envelope-from portmaster@bsdforge.com) MIME-Version: 1.0 Date: Wed, 28 Apr 2021 11:03:34 -0700 From: Chris To: freebsd-ports Subject: When will git be supported for ports? User-Agent: UDNSMS/17.0 Message-ID: <08eb32f6fb033f8590a6f2b181436119@bsdforge.com> X-Sender: portmaster@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4FVmhX50Lmz3CCb X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] 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: Wed, 28 Apr 2021 18:03:25 -0000 Hi all, Maintainer for some ~160 ports, and attempting to fix some bugs. But as I understand it 'git' is supposed to be the new source of truth. While I know svn by heart. I have near zero understanding of git, or for that matter, why anyone would rather use it. That said; as I try to discover the new procedures for maintaining ports under git. I see there isn't anything in the porters-handbook regarding the acquisition of the ports tree in order to get started. Shouldn't this be at the very beginning of the ports doc? The closest thing I could find was a reference to a link: #ports-using/ in the Handbook. Which doesn't exist. It *should* throw a 404. But was cleverly masked, and simply returns the front page. This is a terrible idea. As the doc maintainers will never know they need to make corrections, and new users with a new interest in FreeBSD will become frustrated and turn away. Maintainers, like me, utilizing what little time they have to spare will also become frustrated and likely find that they now only have the time to discover where the actual information is. With no more time to actually *fix* the port they sought to. While I realize this should probably be sent to docs@ I'm not on the list, and because this is ports related. I hope it finds value here as well. Thanks for listening. --Chris