-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 zooko wrote:
It would probably be a lot easier to improve the platform string generation and comparison logic, as has been done for OS X.
As PJE has mentioned, the intent is that the egg name should contain enough information to decide if that egg will work on your platform. For example, if it says "py2.5-win32" then you know it will work on your Python 2.5 on 32-bit Windows, and if it says "py2.5-macosx-10.3- ppc" then you know it will work on your PowerPC-based Mac with Python 2.5. This can be used for example by easy_install to get a directory listing of eggs and choose which one will work on the local platform based solely on its filename.
As PJE mentioned, it would be nice if this same technique worked on Linux.
However, it currently doesn't. Eggs built on Linux are named something like py2.5-Linux-x86_64. To know whether such an egg would actually work on your Linux system, you would also need to know whether the Python was compiled with UCS-2 or UCS-4 internal unicode representation, as well as what version of glibc you have. Is there anything else that would need to be added into the egg name?
Better: just don't distribute binary eggs for Linux at all: - Developers have the tools (or can install them) to build from 'sdists'. - Systems without tools are "locked down", which means that they shouldn't be installing from public distributions anyway: the folks who run them should be able to build *private* eggs from 'sdists' which are known to work for their systems. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ4g3k+gerLs4ltQ4RAjepAKDK9/Y7Gq218CtUOw2KRtAkbLYcWACgtYF5 ogSEjrYyCWzliUo5/jHGm94= =4smt -----END PGP SIGNATURE-----