August 11, 2007 at 05:23 · Filed under apps
I think I may have stumbled upon the answer. I’m so set in my CVS ways that I though the best thing was to branch the entire top level folder – recursively. What I really was after was a way of setting the configspec on the NEW view I create for the new branch, and making it show code that is labeled with a particcular label, then when it is checked out and in, a new revision exists on the new branch. The advantage here, is that my new view shows exactly what I need without the need for checking out a version of every file in that view.
This post over at the IBM Rational Clearcase forums describes EXACTLY what I was after, and explained it in the precise terms I needed. I’m thinking differently now, and if it works as I intend, then I shall write further about this adventure into SCM.
August 7, 2007 at 23:56 · Filed under unix
I’m so used to making branches in CVS.
cvs tag -b system_test
As the CVS doco states simply, “This splits off a branch based on the current revisions in the working copy”, and these revisions will get assigned the branch name, in this case `system_test’. Simple, powerful enough and quick!
But Rational Clearcase is a different beast as I learn it. You have to make your branchtype.
cleartool mkbr system_test
All good so far.
Next I must merge stuff from the current mainline to my new branch, BUT I can only do it a file at a time or using findmerge??? When I do a dry run, the element does not exist in the new branch though so it says it will skip everything… Hmmm
On top of all this one must not forget to set your view configspec set to show this branch! (like a CVS Checkout with your branch tag being sticky).
No wonder people prefer CVS. Clearcase IS powerful once you know it, but the learning curve is huge.
So asking for help – if anyone actually reads this – any quick ways to branch the /main/LATEST into my new branch?
