From owner-freebsd-current Sun Feb 20 14:18: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8248137BFF5; Sun, 20 Feb 2000 14:18:01 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA42492; Sun, 20 Feb 2000 14:15:21 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 20 Feb 2000 14:15:20 -0800 (PST) From: Kris Kennaway To: "David O'Brien" Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: <20000220132647.H14682@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, David O'Brien wrote: > > 2. What they do appears to be kind of icky, e.g. it requires more > > "hand work" than I think the average FreeBSD user would be willing > > to accept > > By handwork you man building, or installing? When I put OpenBSD 2.6 on > my sparc5, I did a normal install and then ftp'ed down the proper > ssl-base package. Then a simple pkg_add. Since OpenBSD does not have > our ``pkg_add -r'' functionalitiy, it wasn't as simple as we could make > it. Err, David, that's exactly the same as our system then. OpenBSD's handling of OpenSSL is bad in other ways, but in this regard it's exactly what we do now. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message