[Fink-devel] python and crypto

2003-03-22 Thread chixson
Not that I'm a core developer or anything, but it seems that python 2.2 linked against ssl as well, and there was never any controversy about it. I guess I don't understand why it's become an issue now. [fourshadows:lib/python2.2/lib-dynload] chixson% pwd /sw/lib/python2.2/lib-dynload [fourshad

Re: [Fink-devel] python and crypto

2003-03-22 Thread Ben Hines
On Saturday, March 22, 2003, at 09:21 AM, Max Horn wrote: Am Samstag, 22.03.03 um 02:46 Uhr schrieb Ben Hines: On Friday, March 21, 2003, at 10:50 AM, Max Horn wrote: I guess that would amount to having python, python-ssl, python-nox and python-nox-sll. Furthermore, there are the 21, 22 and 2

Re: [Fink-devel] python and crypto

2003-03-22 Thread chixson
On Sat, 22 Mar 2003, David R. Morrison wrote: > > Somewhere in the 2.x releases, python picked up ssl socket support, > > Do you know if there is any way to disable this? Well, I've not had time to test anything but here are some ideas: try configuring with: ./configure --without-ssl I'm no

Re: [Fink-devel] python and crypto

2003-03-22 Thread David R. Morrison
[EMAIL PROTECTED] wrote: > Somewhere in the 2.x releases, python picked up ssl socket support, > located in: > > /sw/lib/python2.3/lib-dynload/_ssl.so > > At the very least, this library links against openssl. > Others might, but I'm not aware of them. Do you know if there is any way to disabl

Re: [Fink-devel] python and crypto

2003-03-22 Thread chixson
On Sat, 22 Mar 2003, David R. Morrison wrote: > BTW, I can't figure out why python has an openssl dependency at all. > Neither the binaries nor the library are linked to the openssl lib. > > Still checking into this... Somewhere in the 2.x releases, python picked up ssl socket support, locate

Re: [Fink-devel] python and crypto

2003-03-22 Thread David R. Morrison
BTW, I can't figure out why python has an openssl dependency at all. Neither the binaries nor the library are linked to the openssl lib. Still checking into this... -- Dave --- This SF.net email is sponsored by:Crypto Challenge is now open!

Re: [Fink-devel] python and crypto

2003-03-22 Thread Max Horn
Am Samstag, 22.03.03 um 02:46 Uhr schrieb Ben Hines: On Friday, March 21, 2003, at 10:50 AM, Max Horn wrote: I guess that would amount to having python, python-ssl, python-nox and python-nox-sll. Furthermore, there are the 21, 22 and 23 versions of it, for a total of 12 packages (not counting

Re: [Fink-devel] python and crypto

2003-03-21 Thread Ben Hines
On Friday, March 21, 2003, at 10:50 AM, Max Horn wrote: I guess that would amount to having python, python-ssl, python-nox and python-nox-sll. Furthermore, there are the 21, 22 and 23 versions of it, for a total of 12 packages (not counting splitoffs). Ouch. Maybe a system-python is needed aft

Re: [Fink-devel] python and crypto

2003-03-21 Thread Max Horn
Am Freitag, 21.03.03 um 14:32 Uhr schrieb David R. Morrison: Dear fink developers, Because python is now in the crypto tree, everything that depends or builddepends on python should (in principle) be moved to the crypto tree. Around 20 or 25 currently-stable packages would be affected, and seve

Re: [Fink-devel] python and crypto

2003-03-21 Thread Benjamin Reed
David R. Morrison wrote: Dear fink developers, Because python is now in the crypto tree, everything that depends or builddepends on python should (in principle) be moved to the crypto tree. Around 20 or 25 currently-stable packages would be affected, and several tricky issues would be raised. (On

[Fink-devel] python and crypto

2003-03-21 Thread David R. Morrison
Dear fink developers, Because python is now in the crypto tree, everything that depends or builddepends on python should (in principle) be moved to the crypto tree. Around 20 or 25 currently-stable packages would be affected, and several tricky issues would be raised. (One of the tricky issues is