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/python
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
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
On Thu, 27 Feb 2003 [EMAIL PROTECTED] wrote:
> Andrea and Max: I have had users requesting a python23 package - that's
> why I put it there (in unstable only). You can easily switch back to
> python22 if you want - "fink install python-2.2.2-4". And for what it's
> worth, in my experience pyt
On Sat, 8 Feb 2003, Ben Hines wrote:
> > How long can I expect the older version to be around?
> >
>
> Forever. Calm down. You can go back to the old one. I'll fix your
> package.
Was never not calm, but thanks for the info. I'm actually a bit suprised
that you don't want to phase it out...
I'm the maintainer of the m2crypto package, which gives python access to
the openssl libraries.
It has been confirmed that this package is incompatable with openssl
0.9.7. I've emailed the author and am currently waiting on a relpy.
My question is, what is the timeline before the older openssl
I'm the maintainer for the m2crypto package, and since the upgrade to
openssl-0.9.7 m2crypto will not build on my machine.
I've fixed the problem on my system by reverting to the previous version,
but before I submit a new package doing that, I'd like to confirm that
it really is a problem, and t
I've been working off and on on a package for fink.
The problem is that the install script hardlinks the directory it is
installed in inside a bunch of scripts critical for the performance of the
program.
So, where /sw/bin should be, there is /sw/src/root-*/sw/bin
It would be easiest to just d
Is there way to tell which .deb (and/or package) is responsible for
installing a particular file in /sw?
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_
I had ccp4 installed, until recently, on my machine.
In tracking down why man pages would not display, I discovered the
following:
In system-tetex.csh:
set path = ( $path /usr/local/teTeX/bin/powerpc-apple-darwin-current )
setenv MANPATH /sw/share/xtal/ccp4-4.2.2/man:/usr/man:/usr/local/teTeX/ma
10 matches
Mail list logo
