http://bugs.grommit.com/show_bug.cgi?id=351





------- Comment #3 from richlowe at richlowe.net  2007-12-20 21:07 PDT -------
Notes based on the copy of the ON bits I have (which are not current).

These totally disregard our discussions of which things can go away, it's the
result of a straight grep for teamware/sccs-ish commands and phrases.


gate/daily_snapshot

   Creates the daily workspace with workspace(1), but copies workspace
   content with cpio (and runs an updatenames).

   Hopefully can just be hg clone's, instead.

gate/update_flagdays

   Deals with mail in teamware notification format

gate/putback_diffs

   Deals with mail in teamware format, pokes at things with SCCS

gate/update_SUNWonbld

   does a bringover.  Could do a pull -u instead?

gate/clone_update

   deals with teamware workspace locking, brings over both onnv and IHV.

gate/pbcheck

   deals with teamware format mail notification, should be a real hook

gk/pre-mkdelivery

   locks gates teamwareishly, brings over.

gk/lock-gate

   locks gate teamwareishly

gk/backout

   backs things out SCCS-ishly, should be done Hg-ishly

gk/unlock-gate

   unlocks the gate teamware-ishly

gk/buglist

   trawls putback logs


There maybe more that I missed, but several of these look like they may not be
entirely painful.  Aside from how much is tied to the gate machines.

Changes for the gate being outside, and changes for the gate being in mercurial
are in many places closely equivalent.  Certain things are more than likely
better running inside, for the moment (based on a frequently updating internal
clone?)

I haven't looked especially hard for places where it is assumed that these
scripts are running against the live gate, rather than the clone.  The places
I've seen, however, only make that assumption to the extent that they lock the
gate to do their work, so it does not change under them (as a clone from the
real gate machine would never do...)


-- 
Configure bugmail: http://bugs.grommit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to