/prog/ comments on SCCS

I know there are better systems (SVN, Mercurial, GIT, etc), but we are forced to keep Unix source files on Visual Source Safe (yes, my bosses are Microsoft shitheads)

I only have SCCS available on our Solaris machine, without any chance of installing new software.

Being that SCCS is sooo old... it is worth it to learn?

I thought even Microsoft shitheads had moved on from SourceSafe, or does Team System still cost extra?

>>1,2
Microsoft's official Open Source Community and project hosting site, CodePlex, supports GIT, SVN or Team System.

Microsft's officially sanctioned open source software package repository, CoApp, uses GIT exclusively.

Show your bosses that Microsoft has abandoned VSS.

>>3
Oh, just checked CodePlex now also supports Mercurial in addition to the ones I previously listed.

Note that it does not support VSS.

Using Visual Source Safe in 2011 is like someone still using an unpatched XP pre-SP1 install.

>>1
If your bosses refuse, just fucking set up a local git repository on your workstation and get your coworkers to use it without telling your bosses, just make sure your machine gets back up.

Then when your bosses see that your productivity is increased and there are less merge headaches, drop the bomb.

I've done this so many times, and it works so long as you make them money. If it doesn't and you get the can, be glad you won't have to work there anymore.

I see this all over.  What exactly do you gain by using one source control system over another?  I've never seen any significant difference in behavior between VSS and SVN for example.

>>7
Quality of Tortoisefoo support?

>>8
speaking of >>, all I ever see when Tortoise SVN gets confused is >>>>>>>OH THORRY GUYTH I GOT MIKTHED UP HERE HUHN HUHN instead of a merge tool

>>9
Tortoise SVN works best when you're the only person working on the project.

It r a fact. I know it because of my learnings.

>>10
All projects work best if they're one-man shows.

>>7
VSS doesn't support checking out more than one working copies of the same repository. If you do, it may get confused about which one you're working on and eg. check in changes from another working copy than which you intended. Its branching and merging support is best described as non-existent. It's slow as fuck even when the server is in the same building on GigE (but SVN is not significantly better if you have to go further back in history). The repositories are prone to breakage. The fact that it is best practice to periodically dump and restore the repository database should be enough reason by itself to never use it for anything at all, ever.