Changes by: Aleksey Nogin (nogin at cs.caltech.edu)
Date: 2005-05-12 23:11:06 -0700 (Thu, 12 May 2005)
Revision: 1007
Log message:

      Actually, I have to take this all back :-(. OMConfigure does _not_ seem to be
      a workable solution ATM. The problem is that the .omo file whould normally go
      into ~/.omake/cache which may be NFS-shared between many machines with
      different version of TeTeX and other similar programs. So, unless we decide to
      use something like ~/.omake/`hostname`-cache in place of ~/.omake/cache, this
      is not the way to go.
      

Changes	Path
Properties	omake
+0 -1	omake/.cvsignore
+2 -7	omake/Makefile.in
+4 -5	omake/Makefile.nt
Deleted	omake/OMConfigure
+3 -8	omake/OMakefile.in
Deleted	omake/OMakeroot.src
Added	omake/OMakeroot.src.in
Properties	omake/OMakeroot.src.in
Added	omake/OMakeroot.src.win
Properties	omake/OMakeroot.src.win
+21 -2	omake/configure
+4 -1	omake/configure.in
Deleted	omake/lib/OMakeroot.om