1. RcsLite implements the subset of RCS that TWiki uses.
2. RcsLite is as fast (often faster) because it doesn't have to exec RCS programs.
3. RcsWrap? is a PITA on any platform without a pre-installed RCS. it adds unnecessary complexity to the install.

AFAICT the only thing RcsLite does not implement is getRevisionAtTime, which is exported via Func and needs to be implemented anyway.

By all means keep RcsWrap? as an alternative, but IMHO RcsLite should be the default store implementation system for DakarRelease.

Any counter-arguments?

-- CrawfordCurrie - 21 Jun 2005

i've previously wondered the same thing - as i've run RcsWrap? on a number of servers, either windows, or hosted without rcs (which is why i fixed the bugs i (and Matt ) found.

so a big yes vote from me (from memory it is now also safe to switch between the 2, but tests are needed to ensure it is fully compilant)

-- SvenDowideit - 21 Jun 2005

Further to this, I did some research on RcsLite and found some nasty inefficiencies and at least one downright bug.... so a precondition of this needs to be a decent set of unit tests for RcsLite.

-- CrawfordCurrie - 22 Jun 2005

I improved the RcsLite tests, and have been running RcsLite myself for a while now. Performance is pretty crap, though, which makes me think making it the default is not a good idea.

-- CrawfordCurrie - 08 Jul 2005

I think it is better to stick with RCS...

-- ThomasWeigert - 08 Jul 2005