Date: Sat, 30 Dec 2006 22:43:07 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Paul Schmehl <pauls@utdallas.edu> Cc: Jeremy Chadwick <koitsu@FreeBSD.org>, Mike Durian <durian@shadetreesoftware.com>, freebsd-ports@freebsd.org Subject: Re: www/libwww and SSL Message-ID: <45975BFB.2050604@FreeBSD.org> In-Reply-To: <54DC7293385544FE17F45902@paul-schmehls-powerbook59.local> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45975BFB.2050604>