From owner-freebsd-ports@freebsd.org  Wed Apr 28 18:15:20 2021
Return-Path: <owner-freebsd-ports@freebsd.org>
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 59B415FC3EC
 for <freebsd-ports@mailman.nyi.freebsd.org>;
 Wed, 28 Apr 2021 18:15:20 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 4FVmyJ0yfLz3CYM
 for <freebsd-ports@freebsd.org>; Wed, 28 Apr 2021 18:15:19 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: from pi by home.opsec.eu with local (Exim 4.94 (FreeBSD))
 (envelope-from <pi@freebsd.org>)
 id 1lboiL-00072w-Co; Wed, 28 Apr 2021 20:15:09 +0200
Date: Wed, 28 Apr 2021 20:15:09 +0200
From: Kurt Jaeger <pi@freebsd.org>
To: Chris <portmaster@bsdforge.com>
Cc: freebsd-ports <freebsd-ports@freebsd.org>
Subject: Re: When will git be supported for ports?
Message-ID: <YImmLeTF6mcc6Aln@home.opsec.eu>
References: <08eb32f6fb033f8590a6f2b181436119@bsdforge.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <08eb32f6fb033f8590a6f2b181436119@bsdforge.com>
X-Rspamd-Queue-Id: 4FVmyJ0yfLz3CYM
X-Spamd-Bar: /
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [0.00 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Apr 2021 18:15:20 -0000

Hi!

> 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.

The 'why' was explained here:

https://github.com/bsdimp/freebsd-git-docs/

But, unfortunatly, that text moved somewhere. It's a good
first test to find out how to recover that text from the git repo 8}
Any hints ?

> 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?

This below should work, and I agree with you: It was hard to find out.

mkdir -p somedir/ports
cd somedir
git clone -o freebsd \
	--config remote.freebsd.fetch='+refs/notes/*:refs/notes/*' \
	https://git.freebsd.org/ports.git ports

I'm also trying to learn more git to be able to work on the
ports tree, but my time is limited and somehow, I still do
not see the forest for the trees 8-(

-- 
pi@opsec.eu            +49 171 3101372                    Now what ?