In a cross-plattform development environment, something that only works in windows is terribly restrictive. Its even worse, if there are no Linux clients available. In this case the dilema is Visual Source Safe. While a good package overall, I have identified the following shortcomings:
- No good rollout process.
- Server application is Windows only.
- Client application is Windows only. I haven’t been able to find a Linux client for this.
- In order to access the VSS database on a remote computer, you need to have VSS installed locally.
What I am looking for:
- A cross-plattform solution that provides clients for at least Windows and Linux.
- The server application itself can run on a windows box, but a solution that caters to at least Linux and Windows is preferrable.
- A system that supports incremental rollouts and patches, concurrent versioning, multi-checkout capable, …
So far I’ve come accross the following:
- JEDI CVS
- CVSGUI: graphical frontends for various CVS-based systems.
- TortoiseCVS: a windows client for CVS.
- GNU CVS: opensource CVS system.
Research to be continued on the various available packages…
2 Responses to "Cross-Plattform Versioning System: In the search for an alternative to VSS!"
Anonymous
go for svn.
Mike
Yea, I have been enviously looking at SVN. Unfortunately it only runs on *nix systems. Our development environment runs on Windows machines only.
I have also found that the development software to be used will dictate what versionsing software will be used. For example, developing PHP applications with Zend Studio will require either CVS or SVN, while developing with VisualStudio will require VisualSourceSafe. To that end we have decided to go with VSS2K5. Our PHP development will be done in VS.NET2K5 with the VS.PHP plugin. In our circumstance (due to the windows environment) this is the best solution. For any other solution I would recomment SVN as well.