What to do about RCS/OpenRCS

[Lyndon Nerenberg]

On May 9, 2015, at 8:05 AM, Pedro Giffuni <pfg at FreeBSD.org> wrote:

> We do that with GNU code anyways. The latest (GPLv3) version
> of RCS has already diverged and is incompatible for some third
> party software so we basically ran out of support from upstream.
> OpenRCS has it's own share of problems but generally we can work
> with the OpenBSD maintainers to get things to improve.

But really, how often does the RCS code change?  This is a piece of software you get running once, and then leave alone.  The last thing we want is for it to start growing "features" :-P

There seems to be an ever-increasing paranoia about adopting code in the base.  Are we going to end up at the point where /usr/src/ is nothing but a bunch of Makefiles with VPATH pointed at /usr/src/contrib?  I get it for large outside components that are moving targets (e.g. llvm).  But RCS?  I think the paranoia might be a bit overdone in this case.

--lyndon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20150509/0c685864/attachment.sig>