Don't forget the "-brtype br1,br2,etc" restriction option!
:-)
Jonathan
--- "A Better Solution, Inc." <cciug@abs-consulting.com> wrote:
>
> After further thought... here is a better solution (pun had
> to.) small
> tweak... well at least it requires no code:
>
> cleartool mklbtype -c "The newest version on any branch of
> this element" NEWEST
> cleartool mktrtype -ele -all -post checkin -mklabel NEWEST
> keep_fresh
>
> No trigger code to write.. AND it will cause no other triggers
> to fire...
> (if you have some on mklabel for other policy)
> -Charles
>
>
>
>
> At 07:01 PM 7/5/2001 -0400, A Better Solution, Inc. wrote:
>
> >Jonathan,
> >
> >Sounds good to me... see you at the RUC...
> >
> >-Charles
> >
> >Try ClearTrigger and ClearTrigger Lite at
> http://www.abs-consulting.com
> >
> > A Better Solution, Inc.
> >----------------------------------------------------
> >Charles Clarke III ClearCase Consultant
> >A Better Solution, Inc. (770) 252-1500 x22 [phone]
> >1973 East Hwy. 34
> >Newnan, Ga. 30265 (770) 252-1501 [fax]
> > Email:
> > charles@abs-consulting.com
> >
> http://www.abs-consulting.com
> >
> > At 03:20 PM 7/5/2001 -0700, The Great Vobadmin wrote:
> >
> >>Hmmm...
> >>
> >>It would seem to me you'd have to do some
> >>scripting to determine the latest version
> >>(date/time) from a series of branches.
> >>
> >>I would consider placing a label on the
> >>checked in version in the post-op checkin
> >>trigger. So for branches br1, br2, br3 &
> >>br4, this trigger would fire, moving the
> >>label "BR-LATEST" upon each checkin applying
> >>it to the checked in version on those branches.
> >>
> >>Your configspec would then select the label:
> >>element * BR-LATEST
> >>
> >>Jonathan
> >>
> >>--- Christian Goetze <cg@digisle.net> wrote:
> >> >
> >> >
> >> >
> >> > On Thu, 5 Jul 2001, Berend Ozceri wrote:
> >> >
> >> > > > [...] /main/branch_A and /main/branch_B
> >> > > >
> >> > > > You want to pick the version of element_1 that
> >> > > > was most recently checked in?
> >> > >
> >> > > Correct. I realize that my original message was a bit
> >> > careless in its use
> >> > > of the word "latest." I mean latest in the date/time
> sense,
> >> > not in the
> >> > > version sense.
> >> >
> >> > I'd be interested in understanding the change process
> where
> >> > such a
> >> > selection rule will give you a consistent set of code.
> >> > --
> >> > cg
> >> >
> >> > - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - -
> >> > -
> >> >
> with
> >> > body
> >> > can
> also
> >> > unsubscribe
> >> > customers-only
> >> > website
> >> >
> >>http://clearcase.rational.com/cciug/mailing_list.html
> >>
> >>
> >>__________________________________________________
> >>Do You Yahoo!?
> >>Get personalized email addresses from Yahoo! Mail
> >>http://personal.mail.yahoo.com/
> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - -
> >> with
> body
> >> can also
> unsubscribe
> >> customers-only
> website
> >>
> http://clearcase.rational.com/cciug/mailing_list.html
> >
> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> -
> > with
> body
> > can also
> unsubscribe
> > customers-only
> website
> >
> http://clearcase.rational.com/cciug/mailing_list.html
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> -
> with
> body
> can also
> unsubscribe
> customers-only
> website
>
http://clearcase.rational.com/cciug/mailing_list.html
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:53 EDT