From owner-freebsd-arch Thu Aug 1 14: 0: 1 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C19337B400; Thu, 1 Aug 2002 13:59:57 -0700 (PDT) Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1501F43E42; Thu, 1 Aug 2002 13:59:57 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0503.cvx22-bradley.dialup.earthlink.net ([209.179.199.248] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 17aN35-000744-00; Thu, 01 Aug 2002 13:59:55 -0700 Message-ID: <3D49A115.22FF6948@mindspring.com> Date: Thu, 01 Aug 2002 13:59:01 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jacques A. Vidrine" Cc: Mikhail Teterin , Alexandr Kovalenko , arch@FreeBSD.ORG Subject: Re: OpenSSL vs. -lmd References: <200207311641.g6VGfRWj099655@freefall.freebsd.org> <20020801143059.GA536@nevermind.kiev.ua> <200208011151.55478.mi+mx@aldan.algebra.com> <3D498FB4.6987B696@mindspring.com> <20020801195640.GQ26797@madman.nectar.cc> <3D4998F9.A736EA85@mindspring.com> <20020801203601.GA27367@madman.nectar.cc> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Jacques A. Vidrine" wrote: > > 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. > > That's not true --- there are plenty of applications which use > OpenSSL, and that build find on FreeBSD and other platforms, without > explicit knowledge of what FreeBSD has or does not have in the base > system. I can't help but feel that I am completely missing your > meaning, since surely you cannot be unaware of that fact, or of the > existence and function of things like `autoconf' designed to address > that exact issue. No. The "autoconf" model is inherently broken. Things like "Imake" and "xmkmf" address this exact issue... still, they are suboptimal. You still aren't getting it though: as a software vendor, I want to *avoid* platform dependencies, because platform dependencies cost me. *Someone* has to hack up the platform dependent bits of autoconf. I guess the best way to say it is this: "autoconf is to portability as localization is to internationalization" By including OpenSSL in the base system, you damage the portability of *my* code, if I use FreeBSD as a developement platform. There are also the programs and the header files that OpenSSL would prefer to install into the directories /usr/local/bin and /usr/local/include/openssl, by default, which get installed wherever on FreeBSD. Maybe I'm just upset that OpenSSH was recently trojaned... but it would be nice if I could opt out of inherent system breakages. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message