I recently starting using Clearcase for versioning, at work. I come from a CVS background, so initially found it to be cumbersome. For example, here is how i added a file to the repository:

CVS method:

# Change to your already checked out working folder
cd /your/working/dir
# list folder contents, will see checked out working files
ls -l
# List status of all the files, (optionally, update if needed)
cvs -qn up
# copy in new file to commit
cp ~/yourfile.sh .
# add file to repository
cvs add yourfile.sh
# commit changes, and make add permanent
cvs commit -m "commit message"

Clearcase method:

# Change to your pre-defined clearcase VOB top level folder (will be empty)
cd /your/working/dir
# set your view
cleartool setview [viewname]
# list folder contents, will see working files through "this view"
ls -l
# List status of all the files
cleartool ls -l
# Make current folder checked out for modifications, -nc means no comment
cleartool co -nc .
# copy in new file to commit
cp ~/yourfile.sh
# make new file a new element, and check it in (just like cvs add)
ct mkelem -ci yourfile.sh -c "commit message"
# check in current folder, as modifications are done, -nc means no comment
cleartool ci -nc .
# end your view. your folder is now empty
cleartool endview [viewname]
# release your license (if needed)
clearlicense -release

See? CVS is simpler. But you have to work with what you have. I can see the benefit of Clearcase in a complex development environment. Expect to hear more from me on this tool from IBM.