Date: Thu, 7 May 2015 16:18:38 -0700 From: NGie Cooper <yaneurabeya@gmail.com> To: Pedro Giffuni <pfg@freebsd.org> Cc: Lyndon Nerenberg <lyndon@orthanc.ca>, FreeBSD Current list <freebsd-current@freebsd.org> Subject: Re: What to do about RCS/OpenRCS Message-ID: <CAGHfRMAc4XwqME8Nmi05oy1HBWZZTGLsWoXwkQw3W542GCZB1g@mail.gmail.com> In-Reply-To: <554BCD4C.8090500@FreeBSD.org> References: <554BB84F.7060605@FreeBSD.org> <alpine.BSF.2.20.1505071241240.51250@orthanc.ca> <554BCD4C.8090500@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni <pfg@freebsd.org> 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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGHfRMAc4XwqME8Nmi05oy1HBWZZTGLsWoXwkQw3W542GCZB1g>