Hi,

While reading the PEP I noticed that there seems to be no straightforward  
to specify the package release versions.

   > >> egginfo_dirname('python-ldap', '2.3.10')
   'python_ldap-2.3.10.egg-info'

Consider the following PyPM package file name:

   python-ldap-2.3.10_linux-x86_2.6_2.pypm

Here 2.3.10 is python-ldap's version, 2.6 is the Python version .. and 2  
(the last component) is the binary release number (for ActiveState  
repository). This is to upgrade previous releases of the same python-ldap  
(say, python-ldap-2.3.10_linux-x86_2.6_1.pypm).

If PyPM is to rely on PEP 376 style .egg-info directories (and the RECORD  
files within them), how is it to store/retrieve this release number?  
Currently we store everything (including RECORD) in a sqlite database  
under site-packages. I can continue using the db for release numbers  
alone, but I really prefer that this is covered by a standard that  
evidently provides support for installer tools.

-srid
_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@[...].org
http://mail.python.org/mailman/listinfo/distutils-sig