On Nov 10, 2015, at 5:12 AM, René J.V. Bertin <rjvber...@gmail.com> wrote:
> Indeed. Still, the mod Jeremy introduced is the best/only way I know to allow
> choice that doesn't involve introducing an SSL PortGroup that provides
> +openssl and +libressl variants.
One other way to handle it would be how we tried to handle perl5 for a while
(which doesn’t really work that well for perl, but may apply here).
We could have a port “mp-ssl-lib” that defaults to depending on one of the ssl
libs (say openssl). It could also be installed as mp-ssl-lib +libressl which
would modify it’s dependencies and install libressl and not openssl.
Other ports would all depend on ‘mp-ssl-lib’ and not directly only openssl or
libressl.
It’s not a perfect solution, but may be nicer than adding +openssl/+libressl to
every possible port.
—
Daniel J. Luke
+========================================================+
| *---------------- dl...@geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
