[Distutils] GCC versions and binary egg names

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Withers wrote:
> Hi All,
> 
> In addition to the UCS2/4 problems already described by MAL and which 
> I've bumped into myself, I now have a problem with binary linux eggs 
> where the GCC version doesn't match that of the system the egg is being 
> installed on.

GCC version shouldn't matter.  It is barely possible that libc versions
might.

> Current egg metadata doesn't take either of these into account or even 
> provide a way for the nature of the binary egg to be recorded.
> 
> How're people coping with this?

By never, ever, ever distributing binary eggs, especially for Linux.  An
sdist is nearly always consumable there, with the exception of
deliberately damaged (no tools) lockdown environments:  in such
environments, the dungeonmaster knows exactly which libC / Python is
targeted, and can build / install the binary eggs (privately, please!).

> What are the future plans in this area?

Denying-a-problem-with-the-status-quo'ly ;),


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkxQlQMACgkQ+gerLs4ltQ6NggCgj7kyXbKKIIO54wUZXTqb4KJQ
OO0An3HK5XxMXWMhihetnKvMTBUghFR9
=UXos
-----END PGP SIGNATURE-----