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

[Fred L. Drake, Jr.]

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

Modified Files:
	TODO.txt 
Log Message:
cause zpkg to report an error when multiple resources share the same name;
this previously generated a mysterious traceback when os.mkdir() failed


=== Packages/zpkgtools/doc/TODO.txt 1.13 => 1.14 ===
--- Packages/zpkgtools/doc/TODO.txt:1.13	Tue Apr 27 16:17:55 2004
+++ Packages/zpkgtools/doc/TODO.txt	Tue Apr 27 17:04:12 2004
@@ -17,33 +17,6 @@
   defining package data (common in Zope, but not for everyone).  Low
   priority.
 
-- There needs to be a better error message when two resources use the
-  same name part.  The problem is that ``package:foo`` and
-  ``collection:foo`` both have the same name, and **zpkg** tries to
-  create two different directories of the same name as children of the
-  distribution root.
-
-  Other ways to solve the problem:
-
-  - Remove the resource type from the resource identifier, so names
-    have to be unique to begin with.  Each resource will be expected
-    to identify itself in some way (possibly implicitly, such as by
-    the presence of an *__init__.py* file).  This would mean we need an
-    explicit control of how we deal with dependencies (whether or not
-    we include them in the distribution package, in particular); this
-    would likely be a good thing, but doesn't depend on the change in
-    the resource identifiers.
-
-  - Change the structure of the distribution, so that collection and
-    package resources are located in different directories; for
-    ``collection:foo`` and ``package:foo``, we could end up with::
-
-      foo-x.y/
-          collections/
-              foo/
-          packages/
-              foo/
-
 - Deal with a package tree like the zope package tree that includes
   both pure-Python and non-pure packages; these could easily land in
   separate directory hierarchies for installations using a different