Date: Mon, 17 Jan 2000 09:13:04 -0800 From: Chris Piazza <cpiazza@jaxon.net> To: Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG> Cc: Kris Kennaway <kris@hub.freebsd.org>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile Message-ID: <20000117091304.A1328@norn.ca.eu.org> In-Reply-To: <vqcg0vw68kw.fsf@silvia.hip.berkeley.edu>; from asami@FreeBSD.ORG on Mon, Jan 17, 2000 at 07:06:55AM -0800 References: <Pine.BSF.4.21.0001152125540.84957-100000@hub.freebsd.org> <vqcg0vw68kw.fsf@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 17, 2000 at 07:06:55AM -0800, Satoshi - Ports Wraith - Asami wrote:
> * From: Kris Kennaway <kris@hub.freebsd.org>
>
> * Openssl should now be fully functional for both US and international users
> * - please report any problems you have in using it to me. You should be
> * able to compile all openssl-using code (some of them require rsaref and
> * therefore cannot be used in a commercial setting, others do not), although
> * the ports may need tweaking to deal with the changed base location (/usr
> * instead of /usr/local).
>
> Should I add some stuff to handle the differences in bsd.port.mk (like
> we did with perl5)?
>
> For one thing, openssl is in -current only so we need a way to have
> ports easily depend on the openssl port in -stable.
Actually any port that depends on openssl depends on crypto.1, which
will be found in /usr/lib anyway :). I haven't had any problems
building ports that require openssl, although I'm using the international
version etc.
-Chris
--
cpiazza@jaxon.net cpiazza@FreeBSD.org
Abbotsford, BC, Canada
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000117091304.A1328>