What to do about RCS/OpenRCS

[Pedro Giffuni]

> Il giorno 08/mag/2015, alle ore 00:26, Doug Brewer <brewer.doug at gmail.com> ha scritto:
> 
> On Thu, May 07, 2015 at 04:18:38PM -0700, NGie Cooper wrote: 
> > 
> > On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni <pfg at freebsd.org <mailto:pfg at 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. 
> 
> Confirmed.  Pedro, are you also willing to fix fallout as Xin Li pointed out? 
> If not, please revert, thanks.


I haven’t committed anything to base so there’s nothing to revert (?).

Pedro.
>