httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@hyperreal.org
Subject cvs commit: apache-1.3 STATUS
Date Mon, 21 Sep 1998 12:08:40 GMT
jim         98/09/21 05:08:40

  Modified:    .        STATUS
  Log:
  Looks like we are safe about db1/db2
  compatibility
  
  Revision  Changes    Path
  1.485     +0 -17     apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.484
  retrieving revision 1.485
  diff -u -r1.484 -r1.485
  --- STATUS	1998/09/21 02:30:13	1.484
  +++ STATUS	1998/09/21 12:08:39	1.485
  @@ -44,23 +44,6 @@
   
   RELEASE SHOWSTOPPERS:
   
  -    * DB1.x vs. DB2.x:
  -      Jim: We need to make sure that db2 is backwards compatible with
  -           db1 or else make sure that people know to update their DB
  -	   files (or are we calling db2 files different names?)
  -
  -      Roy: I don't understand why we should stop everything for this.
  -           Does the current cvs work with existing db files, or not?
  -           If not, let's fix it.  If unknown, it isn't a showstopper.
  -
  -      Jim: My concern is that previous versions of Apache were not db2
  -           "aware" best as I can determine. Thus, Apache would use db1
  -	   by default with mod_auth_db.c. Now that Apache "knows" about
  -	   db2, it looks like it prefers that over db1, which means that
  -	   this will break "old" db databases unless db2 can read db1 files.
  -	   I simply don't know if it will, but if it doesn't then this
  -	   looks like a compatibility problem.
  -
       * need to ensure it compiles properly on win32 before rolling the 
         tarball, and that no last minute changes break it
   
  
  
  

Mime
View raw message