From owner-freebsd-ports@FreeBSD.ORG Sun Dec 31 18:19:03 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E6E316A403; Sun, 31 Dec 2006 18:19:03 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id 0523813C46B; Sun, 31 Dec 2006 18:19:02 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (adsl-65-69-140-8.dsl.rcsntx.swbell.net [65.69.140.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 47AF9114307; Sun, 31 Dec 2006 12:15:10 -0600 (CST) Date: Sun, 31 Dec 2006 12:18:51 -0600 From: Paul Schmehl To: Doug Barton Message-ID: In-Reply-To: <45975BFB.2050604@FreeBSD.org> References: <200612291040.29615.durian@shadetreesoftware.com> <20061229190954.GA84882@icarus.home.lan> <1A211FD8C37E9E9379B4526E@paul-schmehls-powerbook59.local> <20061229212658.GA87752@icarus.home.lan> <54DC7293385544FE17F45902@paul-schmehls-powerbook59.local> <45975BFB.2050604@FreeBSD.org> X-Mailer: Mulberry/4.0.7b1 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========79A687210F556ED789C3==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Jeremy Chadwick , Mike Durian , freebsd-ports@freebsd.org Subject: Re: www/libwww and SSL X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2006 18:19:03 -0000 --==========79A687210F556ED789C3========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On December 30, 2006 10:43:07 PM -0800 Doug Barton =20 wrote: > Paul Schmehl wrote: > >> What I want isn't really relevant. I'm simply suggesting that updating >> the port to include an OPTION for with_ssl seems unnecessary *unless* >> someone is going to port sipX. Have you looked at sipX? Porting it >> would not be simple, and I wonder how much demand there would be. In >> any case, *unless* sipX gets ported, it doesn't make sense to me to >> update www/libwww simply to enable an option no one has asked for until >> now. > > OTOH, what harm does it cause? > That depends on how the port is patched. If with_ssl is included in every = build, it's hard to say. There may be many unintended consequences. If=20 with_ssl is included as an OPTION, then when the port is built it will=20 require someone to be at the console (or an entry in /etc/make.conf.) In either case it's a change, and changes should be thought through and=20 tested carefully, *especially* when they're being done to solve one=20 discrete problem rather than adding general functionality that is required = for many things. Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========79A687210F556ED789C3==========--