www/libwww and SSL
koitsu at FreeBSD.org
Fri Dec 29 13:26:59 PST 2006
On Fri, Dec 29, 2006 at 01:58:41PM -0600, Paul Schmehl wrote:
> --On December 29, 2006 11:09:54 AM -0800 Jeremy Chadwick
> <koitsu at FreeBSD.org> 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 |
More information about the freebsd-ports