title: How to track third-party sources with ClearCase without a headache?
body: <p>First of all: I am not an experienced ClearCase user, but I have lots of experience with other VCS and *nix command-line tools. WIth ClearCase, I use command-line tool ("cleartool") working in a Unix shell.</p>
  
  <p>Problem: I have a small set of sources stored in the ClearCase. Once in a while a fresh .tgz with the same sources comes in and I have to update sources in the repository (process could not be changed so that other party will use ClearCase).</p>
  
  <p>Now I do the following:</p>
  
  <ol>
  <li>Extract tgz into, say, "~/new_src"</li>
  <li>"ct setview ..." and cd to the place where the sources are (say, "/vobs/src")</li>
  <li>I compare the sources with "diff -Naurb . ~/new_src", examine diff's output and:
  
  <ol>
  <li>Copy new files to the /vobs/src and do "cleartool mkelem" on them</li>
  <li>Checkout changed files, copy new sources over and commit them</li>
  <li>Do "cleartool mkdir" for new dirs and populate them</li>
  </ol></li>
  </ol>
  
  <p>This process is slowly driving me crazy since in almost any other version control system I would just checkout the sources, copy new sources over, examine diffs, add new files and then commit the whole lot. Or, better yet, use tags/branches, though they are really not needed in this case - I need to have an up-to-date version of the sources in the repo, that's all.</p>
  
  <p>I tried to checkout everything (using "cleartool co -nc <code>find .</code>"), copy new sources over, and commit changed files/add new files afterward. But this requires parsing of the "cleartool ls" output and is even messier.</p>
  
  <p>I could miss something obvious, but several forays into Google tell me that I'm not. However, I'd like to hear it from ClearCase powerusers - is there any hope for clueless like me or not? :)</p>