-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Starting a separate thread from the "formencode as .egg in Debian ??" discussion since this issue is internal to Debian and I don't want DD's to "beat-up" upstream development anymore. :-)
Good or bad python .egg's are here to stay. Following the "formencode as .egg in Debian ??" thread I understand the following. IF Debian decides -not- to support .egg's a few python code bases (modules, applications, etc) will break. Looking into the future more python code bases will move to .egg so the number of broken code bases will only increase. I want to state what I think is the obvious, Debian must support .egg's. NOTE: The implementation of how .egg's are supported can be left to another thread. Is there an agreement amongst the interested debian-python developers/packagers that Debian must support .egg's? Answering the -IF- will let us move forward to the HOW. - -- Bob Tanner <[EMAIL PROTECTED]> | Phone : (952)943-8700 http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500 Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDi1++fPGnCSzBsogRAjI+AJwIQbPm5GWBYSGve4Rfly6nH2FmzACgw1Aa KojmA4grMV/vAyNfDr8qR20= =9tD4 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
