[or-cvs] Define an elaborate set of lunacy to make sure that RPM ver...

[Nick Mathewson]

Update of /home/or/cvsroot/tor/doc
In directory moria.mit.edu:/tmp/cvs-serv22279/doc

Modified Files:
	TODO 
Log Message:

Define an elaborate set of lunacy to make sure that RPM versions do
the right thing with our recalcitrant versioning scheme.  See
tor.spec.in for full details.  Basically, the progression is now:

 Tor version         RPM version
  0.0.8          ---> 0.0.8
  0.0.8.1        ---> 0.0.8.1
  0.0.9pre1-cvs  ---> 0.0.8.99.0.0.9.pre.1.cvs
  0.0.9pre1      ---> 0.0.8.99.0.0.9.pre.1.release
  0.0.9pre2      ---> 0.0.8.99.0.0.9.pre.2.release
  0.0.9rc1       ---> 0.0.8.99.0.0.9.rc.1.release
  0.0.9          ---> 0.0.9
  0.0.9.1-cvs    ---> 0.0.9.0.99.0.0.9.1.cvs
  0.0.9.1        ---> 0.0.9.1

The spec file (but not the system) will break if a tor version ends in
".0", so don't do that yet.



Index: TODO
===================================================================
RCS file: /home/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.217
retrieving revision 1.218
diff -u -d -r1.217 -r1.218
--- TODO	14 Nov 2004 22:08:25 -0000	1.217
+++ TODO	14 Nov 2004 23:18:20 -0000	1.218
@@ -31,13 +31,13 @@
        running-routers so often?
 R  - document signals in man page
    o Check for hibernation on startup, hup, etc.
-N  - Test hibernation a lot.
+N  . Test hibernation a lot.
    o Document all undocumented configuration options.
      o Accounting
      o Control interface authentication
-N  - RPMs
+   o RPMs
      o Merge changes from jbash
-     - Figure out versioning
+     o Figure out versioning
    o Windows installer
      o Make installer get built
      o Write script to correct windows versions.