Noel L Yap wrote:
>
> I'm planning to use ClearCase for a new project
I'm sorry. If you can _possibly_ get away with using CVS, do so.
> 1. Having ClearCase do unreserved checkouts by default.
It's possible. But if you've made changes you don't want to
check in yet, CC doesn't give you the equivalent of "cvs up" to
keep up with the latest.
The recommended way of doing it is for each developer to have
a private branch. Then you can do reserved or unreserved checkouts
on the private branch, and the CC merge tools will help keep the
branch up to date and with merges back to the main. A wonderful
example of how CC turns your every move into a saga.
> 2. Having ClearCase infer which files to operate on (ie
> similar to plain vanilla "cvs ci").
Don't know. How CC internally stores files depends on a heuristic
which is pretty good, ie, binary files are stored compressed, etc.
Note, there is no RCS keyword expansion.
> 3. Having ClearCase do atomic operations (eg either all
> entities specified get checked in or none of them do).
I believe you can lock the vob to prevent others from using
it, which makes it essentially atomic (ie, no half-way state is
possible. But I don't believe it offers "transactions", where
if something doesn't work, you can roll back to a known state.
Regards,
Mitch.
--
| mailto:[EMAIL PROTECTED] | Not the official view of: |
| mailto:[EMAIL PROTECTED] | Australian Calculator Opn |
| Certified Linux Evangelist! | Hewlett Packard Australia |
