[Zope-CVS] CVS: Packages/zpkgtools/doc - TODO.txt:1.51

[Fred L. Drake, Jr.]

Update of /cvs-repository/Packages/zpkgtools/doc
In directory cvs.zope.org:/tmp/cvs-serv17698

Modified Files:
	TODO.txt 
Log Message:
re-organize a bit to reflect priorities


=== Packages/zpkgtools/doc/TODO.txt 1.50 => 1.51 ===
--- Packages/zpkgtools/doc/TODO.txt:1.50	Tue Jun 15 17:33:55 2004
+++ Packages/zpkgtools/doc/TODO.txt	Wed Jun 16 00:43:32 2004
@@ -14,6 +14,24 @@
     distributions or checkouts that use this as the foundation for
     setup.py.
 
+  - When building a distribution that specifies explicit inclusions,
+    the packaging metadata (`*.cfg` except `PACKAGE.cfg`) files should
+    be included automatically.
+
+  - We should have a way to express dependence on particular versions
+    of Python, and a way to say which is preferred.  (This can be used
+    when building an "application" distribution since that has some
+    support to select from different available Python interpreters.)
+
+  - Instead of using setuptools to pick up only the package_data
+    facility, copy the build_py implementation into the **zpkg**
+    runtime package and use it from there.  This removes a large chunk
+    of unused code from distributions (the rest of setuptools).
+
+  - When installing an application bundle, it should be an error if
+    the installation directory already exists and the user hasn't
+    explicitly said that's ok (-f/--force).
+
   - There should be a way to specify a Download-URL when building a
     package; using the distutils "register" command would then cause
     that field to be provided via PyPI.
@@ -23,6 +41,11 @@
     manually.  This doesn't feel like it "plays nice" in the distutils
     world, though.
 
+  - Consider looking for the configuration file in the current
+    directory before looking in ~/.zpkg/.  Note that it's already
+    possible to specify an configuration file, or just add additional
+    resource maps, using command-line options.
+
   - Re-visit the abstractions for parsed revision control URLs:
 
     - The current abstraction is pretty painful to work with, and
@@ -34,11 +57,6 @@
       the generated distribution, instead of having alternate resource
       maps to work from a checkout to access the branch.
 
-  - The setuptools helper should only be included in distributions that
-    actually need it.  This is currenly only needed when packages end up
-    defining package data (common in Zope, but not for everyone).  Low
-    priority.
-
   - CVS retriever (mostly done; need to deal with unspecified type and
     user for remote repositories)
 
@@ -51,15 +69,6 @@
 
     It's not clear these remaining issues are particularly important.
 
-  - When building a distribution that specifies explicit inclusions,
-    the packaging metadata (`*.cfg` except `PACKAGE.cfg`) files should
-    be included automatically.
-
-  - We should have a way to express dependence on particular versions
-    of Python, and a way to say which is preferred.  (This can be used
-    when building an "application" distribution since that has some
-    support to select from different available Python interpreters.)
-
   - Use delayed loading of resource maps, especially those that need to
     be retrieved from remote systems.  The basic model of the resource
     map allows this strategy to be employed effectively.  Low priority.
@@ -73,18 +82,11 @@
     Perhaps a configuration option should specify which are produced
     by default.  Low priority.
 
-  - When installing an application bundle, it should be an error if
-    the installation directory already exists and the user hasn't
-    explicitly said that's ok (-f/--force).
-
   - Some way to transform template files on build or installation
     beyond what distutils does for scripts would be nice; it's not
     clear how to feed enough interesting information into the process.
     The use cases aren't sufficiently clear at this time.  Won't
     happen unless the use cases become clearer.
-
-  - Consider looking for the configuration file in the current
-    directory before looking in ~/.zpkg/.
 
 - Look at the package manager used by the MacPython people to see what
   can be/has been done.