Date: Thu, 01 Aug 2002 21:41:23 +0100 From: Antony T Curtis <antony.t.curtis@ntlworld.com> To: Terry Lambert <tlambert2@mindspring.com> Cc: arch@FreeBSD.ORG Subject: Re: OpenSSL vs. -lmd Message-ID: <3D499CF3.4030601@ntlworld.com> References: <200207311641.g6VGfRWj099655@freefall.freebsd.org> <20020801143059.GA536@nevermind.kiev.ua> <200208011151.55478.mi%2Bmx@aldan.algebra.com> <3D498FB4.6987B696@mindspring.com> <20020801195640.GQ26797@madman.nectar.cc> <3D4998F9.A736EA85@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert wrote: > "Jacques A. Vidrine" wrote: > >>>and is so mixed up >>>in various code that it's hard to keep up with changes for >>>security updates. >> >>Updating it required only some very minor build-infrastructure changes >>outside of src/crypto/openssl. I'm not sure what you mean here. > > > It is hard to update to the latest version of the code on a > FreeBSD 4.6-RELEASE box. <snip> > > No. I mean that I can't build something that will build on > FreeBSD *and* build on some other platform, without having > to inventory all of the implicitly installed packages on FreeBSD > to know which OpenSSL I'm getting. This is why I would like a FreeBSD-Lite... Which is just the core essentials of FreeBSD with everything else (gcc, bind, bash, perl, openssl, openssh etc) coming from the ports. If I had the time, I would be so sorely tempted to roll my own *BSD distribution based on that idea.... FreeBSD without the fluff. I'd have to roll some kind of binary distribution channel as there is no system compiler ;) -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D499CF3.4030601>