From owner-freebsd-ports@FreeBSD.ORG Fri Dec 29 20:31:08 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 34D3116A403; Fri, 29 Dec 2006 20:31:08 +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 0F24313C467; Fri, 29 Dec 2006 20:31:08 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (adsl-66-138-75-58.dsl.rcsntx.swbell.net [66.138.75.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 460C9114307; Fri, 29 Dec 2006 13:55:07 -0600 (CST) Date: Fri, 29 Dec 2006 13:58:41 -0600 From: Paul Schmehl To: Jeremy Chadwick , Mike Durian Message-ID: <1A211FD8C37E9E9379B4526E@paul-schmehls-powerbook59.local> In-Reply-To: <20061229190954.GA84882@icarus.home.lan> References: <200612291040.29615.durian@shadetreesoftware.com> <20061229190954.GA84882@icarus.home.lan> X-Mailer: Mulberry/4.0.7b1 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========781C4230E22BD1D80FE0==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: 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: Fri, 29 Dec 2006 20:31:08 -0000 --==========781C4230E22BD1D80FE0========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On December 29, 2006 11:09:54 AM -0800 Jeremy Chadwick=20 wrote: > > The current maintainer of this port is... no one! :-) Which means, > if you could submit a patch, that'd be great. > > Keep in mind that the change involved will require more than just a > simple Makefile tweak. You will also need to update pkg-plist to > keep track of the extra libraries installed, any extra documentation, > or utilities as a result of --with-ssl. Since there's a shared > library involved, you should also use USE_LDCONFIG=3Dyes to update > the ld.so cache. Is a patch really necessary? The port was created in 1996. There's been=20 no further development of the software since 12 Jun, 2002. This is=20 apparently the first time someone has even noticed the lack of an option=20 to include a make arg for ssl. It seems that a one-off request is hardly=20 reason to update the port. If someone wants to port sipX, then libwww would have to be built with=20 ssl, but I doubt that should be the default anyway. If it should, it=20 would certainly take some testing to see what effect it had all the other=20 ports for which it is a dependency (which is quite a few, I believe.) Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========781C4230E22BD1D80FE0==========--