No update for a day on ports?

Bob Eager rde at tavi.co.uk
Thu Apr 1 08:55:36 UTC 2021


On Thu, 1 Apr 2021 19:47:01 +1100
Dewayne Geraghty <dewayne at heuristicsystems.com.au> wrote:

> Would appreciate if anyone can provide insight as to the 4 git
> commands that I need to function, in a manner similar to the way I
> use svnlite use.  Git equivalents for:
> 
> svnlite update /usr/ports
> svnlite update -r '{$YYYY-$MM-$DD}' /usr/ports/$category/$port
> svnlite log -l $N /usr/ports/$category/$port
> svnlite diff /usr/ports/$category/$port

I got a partial answer. There is a port, net/gitup, that will do an
update of sorts. (Note: I was just told 'gitup' and there is an old
port, now renamed 'git-up', which is not the right one).
> 
> I'm sure many other users would have a similar usage (and similar
> non-knowledge of git)

Indeed. I feel this should have been done in advance. And been in
Appendix A of the Handbook in plenty of time.

> As a minor aside, has anyone stated the reason why the user-base of
> base or ports are moving to git?

Going with the fashion, IMO. But I will no doubt get shouted down.



More information about the freebsd-ports mailing list