Linked by Eugenia Loli-Queru on Fri 20th Feb 2004 06:00 UTC
On Monday, the Subversion project is scheduled to release version 1.0 of their version control system, under development for several years now. Subversion was intended from its inception as the CVS replacement and it comes with many important features previously found only on commercial VCS like Perforce. It was designed for better remote performance, and it is multi-platform with a GUI/CLI front-end.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
What if the DB got corrupt? There is high chance that you will lose everything but its not the same in files. Also the best thing with file is, all existing tools work on it. You can chose your favourite editor or favourite front end to manipulate files in your repository.
When i moved from windows based Version controls like Source safe to CVS and i saw that CVS maintains repository in file system itself, it was a breeze of cool air, i loved the idea so much and now subversion which says will kill CVS is using a database...others may like it..but i don't like it.
Due to this DB thing, i don't think i will ever switch to subversion. I agree that for distributed projects, it may be helpful but even though i am admin of distributed project, i like to have full control. I can easily manage my CVS repository through shell scripts and i have much better control.
For example i can easily print a file in repository and analyze who has done what changes when...i bet it won't be so easy with SVN. I can ftp individual files...treat them the way i want without worrying about DataBase at all.