It's ARK2 time

OK, folks, I'm "flipping over" to the so-called ARK2 stuff.
It's basically:

* a revised "Arusha engine" (in ARK/arkbase); it requires
  different .xml files and changes to Python code that
  wander around in same.

* A bunch of directory and file renamings.

I am switching now because it's the best way to drive
development forward.  (Hey, the whole project is still
"pre-alpha"...)

Lots of consequent activity on the CVS front:

* All the ARK1 stuff has been tagged, and there is a
  orig-ark1-branch for any further development.
  My complete notes are below.

  If you simply want to stay at ARK1 for now, just
  do "cvs update -P -r orig-ark1-branch" in your working
  area for each team of interest.

  Hint: if your name isn't Matt or Will, stick with ARK1.
  Exception: if your name is Jonathan :-)

* I will be totally abusing the HEAD to bring it into ARK2
  line.  I suggest you avoid it.  I'll keep you posted, and
  probably cut some new snapshots soon.

I vaguely plan to give the sourceforge web pages a dusting,
to be "ARK2 compliant".

If, unbeknownst to me, you have a big pile of ARK1 .xml
files that need converting, let me know.  I have a perl
script (which will appear in ARK/ark-convert/cvt-ark1)

Let me know of any issues/problems.  Thanks,

Will

========================================================

* Tag all teams with CVS backing:

  # sourceforge teams:
  CVS_RSH=ssh
  [email protected]:/cvsroot/ark

  for module in ARK arksf1 sample1 sidai simple1 ; do
	cvs rtag orig-ark1 $module
	cvs rtag -b -r orig-ark1 orig-ark1-branch $module
  done

  # glasli1 teams:
  CVSROOT=/d/cvsroot
  for team in glasli1 ; do
	module=ark/$team
	cvs rtag orig-ark1 $module
	cvs rtag -b -r orig-ark1 orig-ark1-branch $module
  done

* Release existing working copies

  (Note: you can update a working copy to be on a branch;
   see below)

  # as appropriate...
  cd ..
  cvs release -d <team>

* Create/checkout new orig-ark1 working copies:

  workspace=/workspace/partain/ark1
  [ -d $workspace ] || mkdir $workspace
  cd $workspace

  # sourceforge teams:
  CVS_RSH=ssh
  [email protected]:/cvsroot/ark
  export CVS_RSH; export CVSROOT

  for module in ARK arksf1 sample1 sidai simple1 ; do
	cvs -z3 checkout -P -r orig-ark1-branch $module
  done

  # glasli1 teams:
  CVSROOT=/d/cvsroot; export CVSROOT
  for team in glasli1 ; do
	module=ark/$team
	cvs checkout -P -r orig-ark1-branch -d $team $module
  done

* Update working copies to be on orig-ark1-branch (directly):

  Note: this is an alternative to doing release/checkout.

  As for checkout, but do "cvs update" instead.

* Create/checkout new HEAD working copies for ARK2.

  same for create/checkout above, but with
  workspace=/workspace/partain/ark
  and no "-r orig-ark1-branch"