From owner-freebsd-current@FreeBSD.ORG Fri May 8 05:27:01 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1BFBF64E; Fri, 8 May 2015 05:27:01 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9B25124B; Fri, 8 May 2015 05:27:00 +0000 (UTC) Received: by wizk4 with SMTP id k4so16218186wiz.1; Thu, 07 May 2015 22:26:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=2Frei6u+gZNhpxz+NWrIE9ljzor96KXcUYprFMgS8Qg=; b=v8rznKBPZyMpNEnWOtSe2J88Z7uynRmq/Y9y7dl1HQLQTL5z2mkOXDOXalLKqhCDyB Ng+7kjKDwVmS81yAuTsJMPBK03SafLVL+NJ9RxacAoJzqUkQ+EExJX/FWRjYCOAujhRg Ee6yqvl1XnE+i4ALaT+N5duDNIneOWp5rlxt+22D6FkCkdz5Z5wLIXFGDyAb8jlxiPn1 X2Yi5PqBhXZ115GaHYpNvrz6wRxI1H0DM1vSyMRappfx5CU0YBSegMQmtJ6JUtn9rZAF YjPQKK5xrwIGG6awxwzeffBeSvMEIjUl1L5GY4dbfzO6K68DYlDz5ukwT7LJrCO5Kllg eotQ== MIME-Version: 1.0 X-Received: by 10.180.10.102 with SMTP id h6mr2749017wib.37.1431062818443; Thu, 07 May 2015 22:26:58 -0700 (PDT) Received: by 10.27.210.147 with HTTP; Thu, 7 May 2015 22:26:58 -0700 (PDT) Date: Fri, 8 May 2015 13:26:58 +0800 Message-ID: Subject: Re: What to do about RCS/OpenRCS From: Doug Brewer To: NGie Cooper , Pedro Giffuni Cc: FreeBSD Current list , Lyndon Nerenberg Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2015 05:27:01 -0000 On Thu, May 07, 2015 at 04:18:38PM -0700, NGie Cooper wrote: > > On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni wrote: > > Hello; > > > > On 05/07/15 14:56, Lyndon Nerenberg wrote: > >> > >> On Thu, 7 May 2015, Pedro Giffuni wrote: > >> > >>> Unfortunately I don't use RCS enough (it looks like I should though) so > >>> I am not in a good position to take the next step and deal with any > >>> fallout it may produce. > >> > >> > >> If we can have a build-knob to disable GNU RCS and enable the new one I > >> will happily twist up the new version and hammer on it. > >> > > > > Yes, that's usually the next step in the process. It is a little bit messy > > because > > there is a WITHOUT_RCS option and openrcs doesn't have rcsfreeze (and > > perhaps something else that we don't use). > > > > I really want to check out first if there is some strong opinion against > > OpenRCS. Perhaps someone that has used it before and thinks it is a > > bad idea. > > > > It looks like there are voices against it, so those have to be addressed > > first. > > Setting WITHOUT_RCS also breaks etcupdate (the tool requires rcs > bits); check with jhb first to make sure that OpenRCS works with > etcupdate. Confirmed. Pedro, are you also willing to fix fallout as Xin Li pointed out? If not, please revert, thanks.