Date: Sat, 10 Dec 2016 18:52:28 +0000 From: bugzilla-noreply@freebsd.org To: perl@FreeBSD.org Subject: [Bug 215197] security/p5-Crypt-SMIME cannot be built with LibreSSL because CMS support is disabled Message-ID: <bug-215197-14331-jtMg4YZ4nk@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215197-14331@https.bugs.freebsd.org/bugzilla/> References: <bug-215197-14331@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215197 --- Comment #10 from John Hein <z7dr6ut7gs@snkmail.com> --- A possible workaround for you is to use DEFAULT_VERSIONS=ssl=base when building security/p5-Crypt-SMIME (you can just put it in your environment). Normally people put DEFAULT_VERSIONS=ssl=XXX in /etc/make.conf to express a preference for using a particular version of ssl (base, openssl, libressl) for _all_ ports builds. But there's nothing to say you can't define DEFAULT_VERSIONS more "surgically" to be different for different ports. There may be complications from doing that, but for a single deviation like this port, you should be okay. There has been some talk of altering what exactly is included in base for ssl (e.g., removing it entirely or using a stripped down version of openssl for just the things that the base OS needs - which would probably _not_ include CMS). So if that talk becomes some form of reality, depending on base for a full-fledged openssl implementation for this port would not be a good long term fix. It seems to me the most fruitful direction would be to work on allowing libressl & openssl to co-exist as ports. I don't think libressl's goals are to be 100% compatible with openssl, so these kinds of problems will always crop up. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215197-14331-jtMg4YZ4nk>