[Zope-Checkins] CVS: Zope - TODO.txt:1.1.2.3

[Chris McDonough]

Update of /cvs-repository/Zope
In directory cvs.zope.org:/tmp/cvs-serv30426

Modified Files:
      Tag: chrism-install-branch
	TODO.txt 
Log Message:
Change setup.py to include logging, Zope.Startup, and Lifetime.  Massage todo.


=== Zope/TODO.txt 1.1.2.2 => 1.1.2.3 ===
--- Zope/TODO.txt:1.1.2.2	Sun Jan  5 00:02:50 2003
+++ Zope/TODO.txt	Sun Jan  5 02:02:51 2003
@@ -17,6 +17,8 @@
  - starting and stopping zope now typically
    performed via "zctl".
 
+ - ZLogger package retired.
+
  - config file placed in instance_home /etc
    directory.
 
@@ -175,8 +177,9 @@
   In the old setup style, "w_pcgi.py" was invoked to install Zope with
   a PCGI ("persistent CGI") socket and files necessary for using Zope
   in conjunction with Apache/IIS.  There are no knobs for installation
-  right now to do the same thing.  The "make_resource.py" file in inst
-  is the only remnant of PCGI support left in Zope.
+  right now to do the same thing.  The 'pcgi' directory still exists
+  in the Zope root dir and the 'make_resource.py' file in "inst" also
+  is available, in case we decide to do something with them.
 
 Update Zope distribution creation machinery
 
@@ -335,13 +338,6 @@
   When Zope starts, it's been asserted in various maillist threads
   that it should chdir to '/'.  This is not done.
 
-Data.fs.in overwritten by zero-byte file at some point during install
-
-  I'm not sure why, but when the branch is set up during "make testinst"
-  (an easy way to set up a branch checkout as both a software_home and
-  instance_home), the build dir's var/Data.fs.in is overwritten with
-  a zero-byte file.  Fix.
-
 Performing the merge
 
   I am not at all confident that doing a cvs up -j
@@ -352,6 +348,20 @@
   /doc directory, the Zope.Startup package, the Zope.App package and
   other necessary files that exist only on the branch in a commit of a
   HEAD checkout.
+
+Review impact of missing Data.fs.in
+
+  The branch install process doesn't copy the "Data.fs.in" file to an
+  instance_home/var directory.  This file is the "initial" filestorage
+  for Zope that gets copied to "Data.fs" during installation in every
+  prior branch of Zope.  This file is evil and must die at some point,
+  and most of the necessary code to set things up properly in the face
+  of an empty Data.fs already exists in OFS.Application.initialize.
+  Things seem to work fine without Data.fs.in but we should just give
+  it a bit of review to see what gets left out, if anything.
+
+  When we find that Data.fs.in isn't necessary, we need to remove it
+  from the HEAD.
 
 Notifying owners of automated testers