SVN: zpkgtools/branches/fdrake-zconfig-branch/doc/TODO.txt remove TODO items that have been done
"Fred L. Drake, Jr." <[email protected]>
| Newsgroups | gmane.comp.web.zope.public-cvs |
|---|---|
| Message-ID | <[email protected]> |
Log message for revision 38167:
remove TODO items that have been done
Changed:
U zpkgtools/branches/fdrake-zconfig-branch/doc/TODO.txt
-=-
Modified: zpkgtools/branches/fdrake-zconfig-branch/doc/TODO.txt
===================================================================
--- zpkgtools/branches/fdrake-zconfig-branch/doc/TODO.txt 2005-08-30 20:42:46 UTC (rev 38166)
+++ zpkgtools/branches/fdrake-zconfig-branch/doc/TODO.txt 2005-08-30 20:45:09 UTC (rev 38167)
@@ -11,15 +11,6 @@
- Package assembler script and distribution runtime
- - It should be possible to simply embed a resoure map within a
- configuration file, so a project can avoid needing two files to
- configure **zpkg**. This might look something like this::
-
- <resources>
- First svn://svn.example.org/repos/main/First/tags/*/
- Second svn://svn.example.org/repos/main/Second/tags/*/
- </resources>
-
- It should be possible to specify a separate resource map for
support code. This would allow the packaging and the distributed
code to remain completely independent.
@@ -101,16 +92,4 @@
- Fix up finddeps.py to stop searching at defined boundaries. How to
define these boundaries is in flux at the moment.
-- Write a new setup.py for Zope 3 and ZODB to use in a checkout that
- uses the package metadata; this can happen after the ZopeX3 release.
-
- A preliminary setup.py replacement for the ZODB project is much
- shorter than the conventional setup.py (28 lines, not including the
- license blurb).
-
- Depending on <load> sections or renamings in <collection> sections
- makes this much more difficult since the sources needed to
- build/install a package may not be available since the distribution
- construction has not been performed.
-
- Documentation, documentation, documentation!
_______________________________________________
Zope-CVS maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-cvs
Zope CVS instructions: http://dev.zope.org/CVS