RE: [cciug] v4.0 and global types

From: Henne, Heinz (Heinz.Henne@nectech.co.uk)
Date: Fri Feb 11 2000 - 05:26:07 EST


Thanks for the solution David, I'll possibly use that as a work around - but
I still think this behavior is wrong. If a type is defined in the AdminVOB
then surely the whole point is that its use in the client should be
seamless, i.e. as if it had been created there anyway? For example, try
doing an lstype -kind brtype in a V4.0 client VOB and you'll see all the
branches defined locally AND in any AdminVOBs, not just the ones that have
been created locally from global types. I can't see any situation where you
would create a global type and then not want it used in a client VOB -
what's the point in that?

Heinz

---
Heinz Henne
ClearCase Administrator
NEC Technologies (UK) Ltd.
Tel: +44 (0) 118 9654535
Email: Heinz.Henne@nectech.co.uk

> ---------- > From: David Boyce[SMTP:dsb@world.std.com > Sent: 10 February 2000 21:35 > To: Marilyn Sander; cciug@Rational.Com; Heinz.Henne@nectech.co.uk > Subject: Re: [cciug] v4.0 and global types > > > At 12:56 PM 2/10/00 -0800, Marilyn Sander wrote: > > >This matches the pre-4.0 behavior. If you define a branch > >type in the admin vob, that type still has to be made > >in the local vob when it's needed. If a local branch type is made > >because a mkbranch rule fires, the branch type is owned by the user > >doing the checkout, not by the owner of the branch type in the admin vob. > > > >It sounds to me as though admin vobs are still not > >ready for prime time. > > No, I don't think this is right. I can't test it right now but I'm pretty > sure this particular problem was fixed in 4.0. > > > When a user performs a mkbranch or checkout with -mkbranch in a > >| client VOB the mkXXtype preop trigger fires and stops the action - even > when > >| that type exists in the admin VOB as a global type. > > This is a bug - in your trigger, which has never had to be admin-vob-aware > > until now. It needs to do a describe on the current vob (available as an > EV) to see it if has an AdminVOB hyperlink. If so, you want to check for > the type in question in the vob pointed to by the hlink. Basically (in > Perl): > > my(@admins) = grep /^->/, qx(cleartool desc -s -ahl AdminVOB > vob:$ENV{CLEARCASE_VOB_PN}); > > David Boyce > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > > http://clearcase.rational.com/cciug/mailing_list.html > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:11 EDT