Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Oct 2020 08:44:14 +0000
From:      Alexey Dokuchaev <danfe@freebsd.org>
To:        Mathieu Arnold <mat@freebsd.org>
Cc:        Kurt Jaeger <pi@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r551373 - in head/dns: . knot3 knot3/files
Message-ID:  <20201006084414.GA93489@FreeBSD.org>
In-Reply-To: <20201005080039.hyfxmx6stfjbazy3@aching.in.mat.cc>
References:  <202010041018.094AI0o8005671@repo.freebsd.org> <20201004102926.GA93206@FreeBSD.org> <20201004103616.GY86683@fc.opsec.eu> <20201004104253.GA10822@FreeBSD.org> <20201005080039.hyfxmx6stfjbazy3@aching.in.mat.cc>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 05, 2020 at 10:00:39AM +0200, Mathieu Arnold wrote:
> On Sun, Oct 04, 2020 at 10:42:53AM +0000, Alexey Dokuchaev wrote:
> > ...
> > Ports cannot be migrated to Git for various reasons.  Even if they
> > could, we're currently using Subversion.
> 
> For the record, ports will be moving to Git within three to six months,
> either before 2021Q1 or if time is too short, 2021Q2.

Per the Core Status Report for 2020-04/05/06, I find this hard to believe.
Conversion to Git is provably feasible for doc and src, but not for ports.
portmgr@ considered a few things implicit in Git as show-stoppers.  Some
members in ports consider lack of tracking renames a show-stopper (I sure
do).  It is definitely the case that SVN currently works well with a mono-
repo and serves us perfectly fine.

Did the Foundation sponsor the work to teach Git how to properly track
renames?  What about sparse and partial tree checkouts and properties,
e.g. keyword expansion?  If there are any no's, I don't see how and why
ports can/should be switched to Git in the near future.

./danfe



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201006084414.GA93489>