EDIT: For RCS specifically, there is an RCS package via Cygwin or an independent package from the Purdue RCS Homepage (the latter says 'The latest PC (OS/2 DOS Win95 NT)', but I guess it might work on Windows 7, I'm fairly sure the Cygwin package works on Win 7). Windows 10, 32-bit* Windows 10, 64-bit*. Complete instructions to purchase and install a Comodo certificate that will allow you to use remote configuration.
I've been using RCS (revision control system) from MKS Source Integrity for several old projects. I have to move to a new Windows 7 computer. The old version I have does not install on Windows 7, and a new version of the software is very expensive.
What is the best free or cheep source of RCS for Windows 7? Also, will it be compatible with MKS Toolkit which I am still going to install?
EugeneEugene
4 Answers
Git (MSysGit) works on Windows 7 and is free. There is a learning curve associated with Git, which I think is worth it (for the benefits you get, especially regarding a distributed VCS), but some may disagree. This bundles come with bash and an ssh client (useful synchronization with remote repositories).
EDIT: For RCS specifically, there is an RCS package via Cygwin or an independent package from the Purdue RCS Homepage (the latter says 'The latest PC (OS/2 DOS Win95 NT)', but I guess it might work on Windows 7, I'm fairly sure the Cygwin package works on Win 7).
BrunoBruno
The official website for RCS has Windows 32-bit binaries, but they are dated. YMMV. http://www.cs.purdue.edu/homes/trinkle/RCS/.
Edit: I just tried the binaries (from the first zip file). They seem to work on a trivial text file.
I put them in a directory. Then I created an 'RCS' directory. Then I created a text file. Then I ran 'set TZ=EST' in my cmd.exe window (the tools require a timezone). Then I was able to check the text file in and out with the RCS command line tools.
Note that large files are probably not supported given the date of the binaries.
If you want the binaries to be available system wide, you have to place them in a location on your Windows PATH and set the TZ environmental variable to the zone you need in your account's environment.
Install Ros On Windows
RCS offers reverse merge which can be useful when you want to apply selected fixes for ECO version of your software without addition on less tested product enhancements. I was able to produce ECO version of real-time control system with several hundred fixes without the assistance of software engineers working on the next release of the product. ClearCase did not offer similar capability at the time.
We used rcs and gmake. Build scripts were written in Perl. Each ran on native Windows. I wish the idiots at the software company in Washington would use / instead of for file separator.
On Windows 7 64-bit SETUP32.EXE fails 'not compatible with the version of Windows you're running'
My workaround:
- Copy sintcm32.dll from a 32-bit machine into c:windowssyswow64.
- In Explorer, double-click a .pj file, set description to 'MKS Source Integrity Project/Sandbox File' and target to '[network location]mkssimkssi32.exe'
- Create start menu shortcuts to '[network location]mkssimkssi32.exe' etc.
Not the answer you're looking for? Browse other questions tagged version-controlwindows-7 or ask your own question.
I'm using GNU RCS version 5.7 for Windows from the official Purdue RCS homepage. If I use the rcsmerge(1) command to merge changes from different branches, I get an error:
every time. Does anyone know why this should happen (and I have seen this problem discussed at least 10 years ago) and what the fix is? Does the GNU current RCS release 5.8.1 fix it? If so, can anyone point me to Windows binaries for this release?
UPDATE 2012-10-22: I have switched the diifutils(cmp, diff, diff3, merge) supplied with the Purdue distribution for the equivalents from the current GNU diffutils 2.8.7. This gets rid of the subsidiary program failed errors, but now gives me The filename, directory name, or volume label syntax is incorrect. exactly twice for each invocation of rcsmerge or diff3. This seems to be a Windows error message.
MaxMax
2 Answers
It looks as if you're missing the diff3.exe binary from your %PATH%. And while it seems that the Purdue packages provide source code for diff3, they don't provide you with a Win32 binary.
If you've already installed diff3.exe from some other source, update your path to include its install location, or (less ideally) move the diff3.exe binary to a folder already named in your path.
If you haven't installed it, you can probably get it from the (ancient) UnxUtils project at SourceForge, or the DiffUtils project.
ghotighoti
Eli Zaretskii has Windows binaries for RCS as part of his ezwinports project at http://sourceforge.net/projects/ezwinports/files.
The README there describes the reason for the problem you describe.
Install Rcs On Windows
RCS-5.7-1: This is a port of the official RCS v5.7.13 source to MS-Windows. I did this port because the existing GnuWin32 port was broken: any RCS command that required running another program as a subprocess (e.g., rcsdiff) would either crash or produce an error message, due to an unhandled problem in the Windows versions of the spawn* library functions.
If I recall correctly the port is unfortunately missing the 'pseudo symlink' feature of the Purdue release. (A quick definition, so as to be self-contained: a pseudo symlink is a text file named 'RCS', located in the same directory as the working file, and whose contents are a directory path, which is treated as a link to a directory containing the master file. Links allow multiple 'working copies' to share a 'repository'.)
Not the answer you're looking for? Browse other questions tagged version-controlrcsthree-way-merge or ask your own question.