[Python-checkins] r73806 - peps/trunk/pep-0376.txt

tarek.ziade python-checkins at python.org
Fri Jul 3 15:21:11 CEST 2009


Author: tarek.ziade
Date: Fri Jul  3 15:21:10 2009
New Revision: 73806

Log:
introduced sys.prefix and sys.exec_prefix in the RECORD file

Modified:
   peps/trunk/pep-0376.txt

Modified: peps/trunk/pep-0376.txt
==============================================================================
--- peps/trunk/pep-0376.txt	(original)
+++ peps/trunk/pep-0376.txt	Fri Jul  3 15:21:10 2009
@@ -216,7 +216,12 @@
 ===============================================
 
 A `RECORD` file is added inside the `.egg-info` directory at installation
-time. The `RECORD` file holds the list of installed files. These correspond
+time when installing a source distribution using the `install` command.
+Notice that when installing a binary distribution created with `bdist` command 
+or a `bdist`-based command, the `RECORD` file will be installed as well since
+these commands use the `install` command to create a binary distributions.
+
+The `RECORD` file holds the list of installed files. These correspond
 to the files listed by the `record` option of the `install` command, and will
 be generated by default. This allows the implementation of an uninstallation
 feature, as explained later in this PEP. The `install` command also provides 
@@ -248,8 +253,13 @@
    path, no matter what the target system is. This makes this information
    cross-compatible and allows simple installations to be relocatable.
 
- - if the installed file is located elsewhere in the system, a
-   '/'-separated absolute path is used.
+ - if the installed file is located under ``sys.prefix`` or 
+   `sys.exec_prefix``, it's a it's a '/'-separated relative path prefixed
+   by the `$PREFIX` or the `$EXEC_PREFIX` string. The `install` command
+   decides which prefix to use depending on the files. For instance if
+   it's an executable script defined in the `scripts` option of the 
+   setup script, `$EXEC_PREFIX` will be used. If `install` doesn't know
+   which prefix to use, `$PREFIX` is preferred.
 
 - the **MD5** hash of the file, encoded in hex. Notice that `pyc` and `pyo`
   generated files don't have any hash because they are automatically produced
@@ -283,7 +293,7 @@
     docutils/__init__.py,b690274f621402dda63bf11ba5373bf2,9544
     docutils/core.py,9c4b84aff68aa55f2e9bf70481b94333,66188
     roman.py,a4b84aff68aa55f2e9bf70481b943D3,234
-    /usr/local/bin/rst2html.py,a4b84aff68aa55f2e9bf70481b943D3,234
+    $EXEC_PREFIX/bin/rst2html.py,a4b84aff68aa55f2e9bf70481b943D3,234
     docutils-0.5-py2.6.egg-info/PKG-INFO,6fe57de576d749536082d8e205b77748,195
     docutils-0.5-py2.6.egg-info/RECORD
 


More information about the Python-checkins mailing list