Port needing security/py-m2crypto built with OpenSSL >=0.9.8

Alejandro Pulver alepulver at FreeBSD.org
Wed Apr 25 01:25:09 UTC 2007


On Mon, 23 Apr 2007 22:11:18 +0200
dirk.meyer at dinoex.sub.org (Dirk Meyer) wrote:

> Hallo Alejandro Pulver,
> 
> > I am making ports for two bittorrent clients based on the ABC one. Both
> > needing py-m2crypto compiled with OpenSSL >=3D 0.9.8.
> > 
> > In my FreeBSD 6.2-RELEASE, for example, I have OpenSSL 0.9.7.x and the
> > py-m2crypto port now uses the one in the base system, so the ports
> > won't work.
> > 
> > Apparently there are 2 ports which use it: net-im/cjc and
> > net-im/py-pyxmpp (by default, not considering optional dependencies).
> > 
> > What would be the best solution? Make it always use the port?
> 
> I liket to suggest you make a slave port of py-m2crypto which use the port.
> 
> Apps are in trouble when they are not linked against the same version.
> so each App should be linked with openssl he same way as its dependencies.
> 
> kind regards Dirk
> 

But there are only 2 ports (grep confirmed it, one is a dependency of
the other) which need it, also it gains more functionality with the new
version (these ports fail because they can't load a python module which
is only available when py-m2crypto uses the new OpenSSL version).

Shouldn't it be better just to make it use the OpenSSL port? Or at
least add a check for the version in the base system (maybe
bsd.openssl.mk should support this)? In most cases users will need the
new version after the addition of these ports.

Best Regards,
Ale
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20070425/fdb9dca0/signature.pgp


More information about the freebsd-ports mailing list