www/libwww and SSL

[Paul Schmehl]

--On December 29, 2006 1:26:58 PM -0800 Jeremy Chadwick 
<koitsu at FreeBSD.org> wrote:

> On Fri, Dec 29, 2006 at 01:58:41PM -0600, Paul Schmehl wrote:
>>
>> 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)
>
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.

> I just want to make sure I'm reading this correctly.

Perhaps my clarification will confirm your suspicions.  Perhaps not.

Paul Schmehl (pauls at utdallas.edu)
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/