From owner-freebsd-current@FreeBSD.ORG Thu May 7 23:18:39 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0ADC3754; Thu, 7 May 2015 23:18:39 +0000 (UTC) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (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 CA37A1C22; Thu, 7 May 2015 23:18:38 +0000 (UTC) Received: by igbyr2 with SMTP id yr2so7355604igb.0; Thu, 07 May 2015 16:18:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nTO0fDTwqLkrm3shc+TIoVFyMZuBEqMId7W7zzrDiP0=; b=VtH3hO2Ht+PzIeiGxYxEOnIv/d9sOESFPEDmih4+owiGWv+F9M7XIKFUuJJDEjc/Pw 6lra95ckL8Oos/RBev4CcDDp528O9N8vZnTb9xSfo2tNSJnAz+1TwsWuKIBPoK7qZfVg 6VT8qoXS3B43ATy9B9IDVHdgxNsOsMshi0ZZmTZZNjRu0HhlukrpNIUSCD1dp3r2kXI3 oZ3+nso4J9D1Ptuy/mnQmKY4HyQpFxawlihPW1gtBLgJ0A9+jB7/Ovn99dbxtjzoRHxD 4xcQRnetmYbZ9o1An//IN9BQfsryybiLYGpVrzFOnEChyyWCyuYwNsGTLW6TfCH1oG/I NzYQ== MIME-Version: 1.0 X-Received: by 10.50.114.35 with SMTP id jd3mr819056igb.14.1431040718180; Thu, 07 May 2015 16:18:38 -0700 (PDT) Received: by 10.107.131.20 with HTTP; Thu, 7 May 2015 16:18:38 -0700 (PDT) In-Reply-To: <554BCD4C.8090500@FreeBSD.org> References: <554BB84F.7060605@FreeBSD.org> <554BCD4C.8090500@FreeBSD.org> Date: Thu, 7 May 2015 16:18:38 -0700 Message-ID: Subject: Re: What to do about RCS/OpenRCS From: NGie Cooper To: Pedro Giffuni Cc: Lyndon Nerenberg , FreeBSD Current list Content-Type: text/plain; charset=UTF-8 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: Thu, 07 May 2015 23:18:39 -0000 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. Cheers!