
Proposal for Elixir/Ohana Software Version Control

Current Practice

- RCS on each file
- source code in /data/elixir2/srcdir/ohana
- some scripts (mana/status/dimm?) in /data/elixir2/srcdir/config/mana
- configuration information in /data/elixir2/srcdir/config
- software compiled in place
- installed in /apps/elixir/bin, /apps/elixir/config

Proposal

- Use CVS to control software versions
- Identify software releases, tag with CVS release tags
- use /data/elixir2/srcdir/ohana as development site (jcc)
- use /cfht/src/eos/

----

work to be done to finish CFHT elixir conversion to CVS:

- verify perl & shell scripts are current
- verify config files are current
- convert to opihi.v2:
  - test mana scripts under opihi.v2
  - move 'status' scripts to 'dvo'
- define a complete set of packages for release

---

In order to convert the operational CFHT version of Elixir / Ohana to
the CVS-controlled version, we need to do several things:

1) merge the changes between the CFHT and IfA trees.

2) move the CFHT version of Ohana to the new opihi.v2 system from the
   opihi.v1 system:
   - move to the name 'dvo' rather than 'status'
   - use the v2 version of mana

3) define the Elixir / Ohana packages and tag them with a starting
   release name 

4) define an initial distribution for Elixir / Ohana using the
   complete set of released packages.

I have been working to unify the CFHT and IfA Elixir / Ohana trees.  I
have imported all of the CFHT version of the entries in the config
directories and the CFHT versions of the shell and perl scripts.  

I have checked on the use of the 'status' program within the Elixir /
Ohana scripts.  I have modified sp_plot and el_plot to use 'dvo'
instead.  I have also modified elixir.photreport.  
