Date: Wed, 28 Apr 2021 11:26:14 -0700 From: Chris <portmaster@bsdforge.com> To: Kurt Jaeger <pi@freebsd.org> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: When will git be supported for ports? Message-ID: <94b9d2e00b27e8da23e86fa9a5651405@bsdforge.com> In-Reply-To: <YImmLeTF6mcc6Aln@home.opsec.eu> References: <08eb32f6fb033f8590a6f2b181436119@bsdforge.com> <YImmLeTF6mcc6Aln@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-04-28 11:15, Kurt Jaeger wrote: > 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-( Kurt, you're AWESOME! Vastly useful, and GREATLY appreciated. :-) Now, if we could only get this $hit in the docs. ;-) Thanks! --Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?94b9d2e00b27e8da23e86fa9a5651405>