Remove file type indicator
Rearrange order of file fields Note that .pyc/.pyo files are listed, too
This commit is contained in:
parent
8dd23c1dcf
commit
4829fd6e55
19
pep-0262.txt
19
pep-0262.txt
|
@ -73,13 +73,16 @@ Database Contents
|
|||
|
||||
FILES section
|
||||
|
||||
An entry for each file installed by the package.
|
||||
XXX Are .pyc and .pyo files in this list? What about compiled
|
||||
.so files? AMK thinks "no" and "yes", respectively.
|
||||
An entry for each file installed by the package. Generated files
|
||||
such as .pyc and .pyo files are on this list as well as the original
|
||||
.py files installed by a package; their checksums won't be stored or
|
||||
checked, though.
|
||||
|
||||
Each file's entry is a single tab-delimited line that contains
|
||||
the following fields:
|
||||
|
||||
* The file's full path, as installed on the system.
|
||||
|
||||
* The file's size
|
||||
|
||||
* The file's permissions, and the owner/group of the file.
|
||||
|
@ -87,16 +90,6 @@ Database Contents
|
|||
|
||||
* An MD5 digest of the file, encoded in hex.
|
||||
|
||||
* The file's full path, as installed on the system. (XXX
|
||||
should it be relative to sys.prefix, or sys.prefix +
|
||||
'/lib/python<version>?' If so, full paths are still needed;
|
||||
consider a package that installs a startup script such as
|
||||
/etc/init.d/zope)
|
||||
|
||||
* XXX some sort of type indicator, to indicate whether this is
|
||||
a Python module, binary module, documentation file, config
|
||||
file? Do we need this?
|
||||
|
||||
A package that uses the Distutils for installation should
|
||||
automatically update the database. Packages that roll their own
|
||||
installation will have to use the database's API to to manually
|
||||
|
|
Loading…
Reference in New Issue