Date: Sat, 29 Aug 2020 11:34:15 -0400 From: Michael Butler <imb@protected-networks.net> To: Glen Barber <gjb@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: documentation on release build process change (svn -> git)? Message-ID: <95d7aef5-69d4-0215-43ca-0663bc370667@protected-networks.net> In-Reply-To: <20200829151406.GA19857@FreeBSD.org> References: <cc3e3579-6ff8-89d4-f713-7672836143a4@protected-networks.net> <20200828174307.GC61041@FreeBSD.org> <20200828174424.GD61041@FreeBSD.org> <aa7989d6-eed5-9575-09bb-536680629e61@protected-networks.net> <20200829151406.GA19857@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/29/20 11:14 AM, Glen Barber wrote: > NOPORTS=yes is the problem, and I forgot to address it before merging > the project branch back. Please try with r364956. Trying now but, in the interim, I noted .. With SVN, I could re-use a previously existing build directory and it would simply apply the relevant diffs to bring the tree up to date. In the move to GIT, now it seems I have to pull the whole tree down or it complains .. imb@vm01:/usr/src/release> sudo ./release.sh -c release-i386.conf fatal: destination path '/usr/local/release-builds/i386/usr/src' already exists and is not an empty directory. I'm not that familiar with GIT but .. Is there an incremental update option I can use? If so, should this be the default? As is, it seems like a colossal waste of bandwidth and unwanted load on the parent GIT repo, imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?95d7aef5-69d4-0215-43ca-0663bc370667>