[Zope-CVS] CVS: Packages/zpkgtools/doc - collections.txt:1.6
Fred L. Drake, Jr.
fred at zope.com
Mon Apr 19 13:17:07 EDT 2004
Update of /cvs-repository/Packages/zpkgtools/doc
In directory cvs.zope.org:/tmp/cvs-serv24081/doc
rename INSTALL.cfg --> SETUP.cfg
=== Packages/zpkgtools/doc/collections.txt 1.5 => 1.6 ===
--- Packages/zpkgtools/doc/collections.txt:1.5 Mon Apr 19 11:20:32 2004
+++ Packages/zpkgtools/doc/collections.txt Mon Apr 19 13:16:36 2004
@@ -114,7 +114,7 @@
- We're not currently loading any sort of "package information" for
collections, but this is a software issue, not a design problem.
- The information file will be called `INSTALL.cfg`.
+ The information file will be called `SETUP.cfg`.
.. include:: links.rst
=== Packages/zpkgtools/doc/metadata.txt 1.10 => 1.11 ===
--- Packages/zpkgtools/doc/metadata.txt:1.10 Mon Apr 19 11:15:06 2004
+++ Packages/zpkgtools/doc/metadata.txt Mon Apr 19 13:16:36 2004
@@ -23,7 +23,7 @@
Dependencies are case-sensitive.
Note that dependencies are kept separate from the information in the
- `INSTALL.cfg` file since that's intended to record information about
+ `SETUP.cfg` file since that's intended to record information about
what the distribution contains, while dependencies serve as
constraints on any software included in the distribution.
@@ -36,11 +36,6 @@
isn't a collection; this name is used since it usually will be a
- This file contains information on building extension modules.
- Information about scripts and documentation files will also be
- included in this file.
General metadata related to a distribution. This includes
information such as the name of the component (i.e., "Frobnitz
@@ -58,10 +53,15 @@
install** build process that creates an application-specific
installation tree (for example, `/usr/local/Zope3`).
+ This file contains information on building extension modules.
+ Information about scripts and documentation files will also be
+ included in this file.
Embedded Package Definitions
-Distribution components can include a `INSTALL.cfg` that contains
+Distribution components can include a `SETUP.cfg` that contains
information about special files in the component (such as
documentation and scripts), and what extensions need to be built.
This file is a ZConfig-like configuration file that can contain the
@@ -82,14 +82,14 @@
`.svn` are ignored, as are files named `.cvsignore`.
Paths can only refer to descendents of the directory containing
-`INSTALL.cfg`, never to that directory itself or anything higher up
+`SETUP.cfg`, never to that directory itself or anything higher up
the filesystem hierarchy.
Support for Compiled Extensions
Compiled extensions are described using **<extension>** sections in
-the `INSTALL.cfg` file. The name of the section should be the name of
+the `SETUP.cfg` file. The name of the section should be the name of
the extension module within the Python package. For example, the
extension ``persistent.cPersistence`` would be represented using a
section of the form::
More information about the Zope-CVS