From owner-freebsd-stable@freebsd.org  Thu Jan 25 15:18:16 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56A06EB4D92
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Thu, 25 Jan 2018 15:18:16 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org
 [52.58.109.202])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D6F1F81720
 for <freebsd-stable@freebsd.org>; Thu, 25 Jan 2018 15:18:15 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: f126e879-01e2-11e8-91c6-33ffc249f3e8
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 73.78.92.27
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [73.78.92.27])
 by outbound1.eu.mailhop.org (Halon) with ESMTPSA
 id f126e879-01e2-11e8-91c6-33ffc249f3e8;
 Thu, 25 Jan 2018 15:18:06 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0PFI5Av011476;
 Thu, 25 Jan 2018 08:18:05 -0700 (MST) (envelope-from ian@freebsd.org)
Message-ID: <1516893485.42536.226.camel@freebsd.org>
Subject: Re: why does buildworld fail on stable/11 ?
From: Ian Lepore <ian@freebsd.org>
To: tech-lists <tech-lists@zyxst.net>, Scott Bennett <bennett@sdf.org>
Cc: freebsd-stable@freebsd.org
Date: Thu, 25 Jan 2018 08:18:05 -0700
In-Reply-To: <5ff60dd8-734c-8b97-3dca-891910299be4@zyxst.net>
References: <201801240851.w0O8pnDl008705@sdf.org>
 <f4e0b36c-12e5-37fb-1c65-d2fc4046c23c@zyxst.net>
 <201801250622.w0P6M3Id020498@sdf.org>
 <5ff60dd8-734c-8b97-3dca-891910299be4@zyxst.net>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 15:18:16 -0000

On Thu, 2018-01-25 at 12:40 +0000, tech-lists wrote:
> 2. I don't know the difference between svnlite and svn. All I know is
> that svnlite is in base and it will be in base for reasons and one of
> those reasons will be that it works reliably. I think svn in ports might
> be more featureful, but maybe it's more buggy because of it, maybe it
> does more - I don't know. In your position I'd like fewer unknowns. I
> mean, even make cleandir fails. In circumstances like that, the first
> thing I'd do is get fresh sources.

The svn in ports is what freebsd committers use.  It works fine.  

svnlite is basically the full svn without the support for things like
perl and python plugins so that base freebsd doesn't have dependencies
on those things.

-- Ian