3 ms·
They are hard to find. Do you know some? All I have is this thread: https://lobste.rs/s/fosip5/should_version_control_build_systems#c_bkq3ve https://lobste.rs/
by qznc 7y ago
They are hard to find. Do you know some?
All I have is this thread: https://lobste.rs/s/fosip5/should_version_control_build_systems#c_bkq3ve https://lobste.rs/s/fosip5/should_version_control_build_syst...
- krupan 7y agoI used clearcase many years ago, and this thread on lobste.rs is pretty accurate and interesting. They point out that the biggest problems were exclusive checkouts, file versioning instead of changesets, and the baked in out of date assumptions about networking. Getting your configspec wrong was a common problem too. At HP we had some in-house perl-script wrappers around the raw clearcase tools that fixed many of these problems. The developers of those scripts had all left to go work for Rational (makers of clearcase), and I don't think anyone really knew how they worked. We also had a full-time clearcase engineer that kept the servers running. Fortunately our smallish projects didn't need the full power of clearcase and those perl scripts kept working fine for us. I did alway wonder what would happen if the one guy who understood the servers left the company. In short, it's a complex and powerful tool that very few people really understood. Very few projects need all that power and complexity. I'm sure Microsoft and Google benefit from complex version control tools and have engineers to spare for managing and understanding them, but I don't think any open source projects or smaller companies are really going to benefit from "clearcase for the modern age" type tools.