SVN: zpkgtools/trunk/doc/TODO.txt document idea about embedding a resource map directly in the configuration file
"Fred L. Drake, Jr." <[email protected]>
| Newsgroups | gmane.comp.web.zope.public-cvs |
|---|---|
| Message-ID | <[email protected]> |
Log message for revision 37745:
document idea about embedding a resource map directly in the configuration file
Changed:
U zpkgtools/trunk/doc/TODO.txt
-=-
Modified: zpkgtools/trunk/doc/TODO.txt
===================================================================
--- zpkgtools/trunk/doc/TODO.txt 2005-08-05 19:47:46 UTC (rev 37744)
+++ zpkgtools/trunk/doc/TODO.txt 2005-08-05 19:54:01 UTC (rev 37745)
@@ -45,6 +45,15 @@
- 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>
+
- 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
_______________________________________________
Zope-CVS maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-cvs
Zope CVS instructions: http://dev.zope.org/CVS