Source Code Repository Software.

Post #26,799 by static 2/1/02 1:03:29 AM Reply	Source Code Repository Software. My colleague/boss and I are neck-deep in programming for our major product. Currently, we use CVS. Works well, but it's a little bit old and he wants things like atomic commits, more flexible versioning (e.g. entire branch), branch merging and meta-data versioning. So far, he's tried something called Arch - wierd build process and we can't find the executable it supposedly made - and SubVersion - couldn't figure out how to create or import whole repositories. What would you guys recommend? Wade. "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #26,817 by wharris2 2/1/02 8:31:34 AM Reply	Re: Source Code Repository Software. Company I'm with uses RCS, but with a built-up system involving Make and lots of stuff... not an easy thing to replicate. "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth
Post #26,840 by Yendor 2/1/02 10:17:03 AM Reply	Re: Source Code Repository Software. Currently at work, we use CVS. It works, just as it does for most of the open-source projects around. It's got some warts, and some things that I don't like about it, but we deal with them. I know one of the developers at [link\|http://www.collab.net/\|collab.net], which is building the Subversion project you mentioned. As I understand it, that project is currently in some form of alpha stage (I don't stay current on the project because I don't use it), but they're due to do a final v1.0 release sometime 1Q or 2Q this year. I'll definitely check it out (no pun intended) at that time, and see if we can't replace CVS here at work. -YendorMike "The problems of the world cannot possibly be solved by the skeptics or the cynics whose horizons are limited by the obvious realities. We need people who dream of things that never were." - John F. Kennedy
Post #26,881 by ben_tilly 2/1/02 1:33:09 PM Reply	You could give Perforce a shot I haven't used it, but that is what is used for perl's source-code and some like it. Cheers, Ben
Post #26,902 by Yendor 2/1/02 3:47:56 PM Reply	Tried it... I tried that around summer 2000. So, my information may be a bit out-of-date as far as experience goes... Perforce is, IIRC, just a little GUI built on top of CVS. It integrates (supposedly) with Your Favorite Tool, but I could never get the .DLL to work with JBuilder, which is the environment I was using at the time. I tried for a few weeks to get it to work. Their sales staff was nice (they wanted to sell it to me, so of course they were.) We could never get multiple users to be able to access the system at the same time, which the demo was supposed to be able to do. Couldn't get "the other" user to see changes that "I" was making. (Which user is which is swappable in this instance.) So, we couldn't get the demo to work properly. Therefore, we didn't buy it. -YendorMike "The problems of the world cannot possibly be solved by the skeptics or the cynics whose horizons are limited by the obvious realities. We need people who dream of things that never were." - John F. Kennedy
Post #27,116 by bconnors 2/3/02 9:21:10 PM Reply	Re: Source Code Repository Software. Is "CVS" the same thing as "PVCS" by Merant? I used that at the last employer for all mainframe source code storage. Worked pretty well. At the job before that we used something from MKS to store the source code files - can't remember the name anymore though. Currently we use Visual Source Safe. It was in place but ignored until I started bitching loudly. I mean, the last checked-in source code module was at least 25 versions ago in some cases, and a few modules were checked out by a guy who quit in 2001, and nobody ever cleaned up after him. Only good thing about VSS is that it stores compiled object files.
Post #27,198 by Yendor 2/4/02 11:57:39 AM Reply	Be careful... Some source code control is better than none, but that point is debatable when the source code control you're using is M$ VSS. I has a tendency to eat its database for lunch once in a while. And, of course, once that happens, you have lost all history. So, that begs the question....Is your source really safe with SourceSafe? -YendorMike "The problems of the world cannot possibly be solved by the skeptics or the cynics whose horizons are limited by the obvious realities. We need people who dream of things that never were." - John F. Kennedy
Post #27,323 by bconnors 2/5/02 12:17:50 AM Reply	I've heard about that before But have no real say in trying to get them to investigate alternatives. It came with the few copies of Visual Studio that they own, so they're using what they already paid for. I've also mentioned to the team leader/contractor about the mulitple articles I've read about VSS going down the black hole, but he just shrugs his shoulders and says "we have backup tapes". This from a place that STILL has the ghost of Nimda/Code Red floating around a few servers as of yesterday. They keep saying that Norton has killed it, but I keep finding .EML and .NWS files on a few of the servers I use daily. I keep current copies of all my projects locally, and bring home files on floppy to keep my CD archive current. BConnors "Prepare for metamorphosis. Ready, Kafka?"
Post #27,201 by wharris2 2/4/02 12:09:42 PM Reply	Based on RCS? I thought PVCS was originally based on RCS. "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth
Post #27,312 by static 2/4/02 9:53:41 PM Reply	Doesn't PVCS cost? The thing is, see, that CVS does nearly all we want. So I'm afraid anything that's non-gratis has to be substantially better for it to be considered. I may not have originally made that point clear. Naturally, if we had the time, we'd simply modify CVS ourselves. Wade. "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #146,923 by Another Scott 3/18/04 1:14:46 PM Reply	Subversion 1.0 is out. [link\|http://www.linuxdevices.com/news/NS2587530479.html\|LinuxDevices] story (from LinuxToday pointer). I have no idea whether it's any good; I just thought I'd pass along the info. Cheers, Scott. (who thought this was a reasonable thread to put this in...)
Post #146,950 by admin 3/18/04 2:45:41 PM Reply	The problem with Subversion is that it needs to be a LOT better than CVS to gain traction. CVS is widely supported... just about everything to do with development supports CVS. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #160,140 by dshellman 6/16/04 2:40:02 PM Reply	Re: The problem with Subversion We are looking into switching from CVS to SubVersion. It provides the ability to do atomic commits; the branching is better, etc. It has plug-ins for most things (i.e. Eclipse, Windows Shell, has it's own GUI, etc.). The import from CVS shouldn't be too difficult (though I expect the importing of branches to be a little tricky, but I don't have first-hand knowledge of this). It's also being used more and more by open source projects, which I expect to continue (might even go so far as to say that as it improves, CVS will give way to SubVersion).
Post #160,141 by admin 6/16/04 2:43:04 PM Reply	I'm using it at home. It's pretty nice. But as I said, inertia counts for a lot. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #160,115 by bluke 6/16/04 11:10:00 AM Reply	What about StarTeam? Where I am we are switching from a home grown system built on RCS to StarTeam. Supposedly they did a benchmark of a whole bunch of tools and picked StarTeam. I am skeptical about the wqhole process. Does anyone know what StarTeam offers over and above CVS for example?
Post #160,118 by admin 6/16/04 11:22:18 AM Reply	StarTeam is OK You could do worse. It only runs on Windows, though, last I used it. This was admittedly a number of years ago, though. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #160,121 by Yendor 6/16/04 12:29:07 PM Reply	Good product We use StarTeam here currently. It runs on both Windows and Linux (contrary to what Mr. Anderson says.) There's a Java-based GUI front-end for Linux that I use daily. It works, but it's a little slow; that might be due to the fact that I'm in Chicago and the server's in Omaha, NE. There's also an Ant integration task for StarTeam, and it can be used in stand-alone command-line mode, too, if you're hardcore (or for use in daily deployment scripts.) We're currently using the command-line mode, because I had already completed writing our daily deployment script when I found out that it has Ant integration. One big thing that I've found it has over CVS is that it's not just source code control, but it tracks Change Requests built-in. So when you check code in, you link it to a particular CR. If you want to back out just that CR's changes, you can find all the source files that CR is linked to, and roll them back, leaving all other changes made during the same time period. NOTE: This feature requires developer discipline, which I'm sure you're aware is less frequent than it should be. -YendorMike [link\|http://www.hope-ride.org/\|http://www.hope-ride.org/]

Welcome to IWETHEY!