From owner-freebsd-ports@FreeBSD.ORG Fri Dec 29 21:26:59 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 6B37616A403 for ; Fri, 29 Dec 2006 21:26:59 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [204.127.192.84]) by mx1.freebsd.org (Postfix) with ESMTP id 55C1D13C441 for ; Fri, 29 Dec 2006 21:26:59 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (rwcrmhc14) with ESMTP id <20061229212658m1400ffga6e>; Fri, 29 Dec 2006 21:26:58 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 62E4F1FA037; Fri, 29 Dec 2006 13:26:58 -0800 (PST) Date: Fri, 29 Dec 2006 13:26:58 -0800 From: Jeremy Chadwick To: Paul Schmehl Message-ID: <20061229212658.GA87752@icarus.home.lan> Mail-Followup-To: Paul Schmehl , Mike Durian , freebsd-ports@freebsd.org References: <200612291040.29615.durian@shadetreesoftware.com> <20061229190954.GA84882@icarus.home.lan> <1A211FD8C37E9E9379B4526E@paul-schmehls-powerbook59.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1A211FD8C37E9E9379B4526E@paul-schmehls-powerbook59.local> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: 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: Fri, 29 Dec 2006 21:26:59 -0000 On Fri, Dec 29, 2006 at 01:58:41PM -0600, Paul Schmehl wrote: > --On December 29, 2006 11:09:54 AM -0800 Jeremy Chadwick > 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=yes to update > >the ld.so cache. > > Is a patch really necessary? The port was created in 1996. There's been > no further development of the software since 12 Jun, 2002. This is > apparently the first time someone has even noticed the lack of an option > to include a make arg for ssl. It seems that a one-off request is hardly > reason to update the port. > > If someone wants to port sipX, then libwww would have to be built with > ssl, but I doubt that should be the default anyway. If it should, it > would certainly take some testing to see what effect it had all the other > ports for which it is a dependency (which is quite a few, I believe.) Am I reading this correctly? You *don't* want www/libwww updated to support WITH_SSL because it's a "one-off request" involving an upstream port dependancy? (re: sipX) I just want to make sure I'm reading this correctly. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |