From owner-freebsd-ports Mon Dec 18 18:33:23 2000 From owner-freebsd-ports@FreeBSD.ORG Mon Dec 18 18:33:21 2000 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 2A2E737B402 for ; Mon, 18 Dec 2000 18:33:21 -0800 (PST) Received: from localhost (kbyanc@localhost) by earth.backplane.com (8.11.1/8.9.3) with ESMTP id eBJ2XKR53044; Mon, 18 Dec 2000 18:33:20 -0800 (PST) (envelope-from kbyanc@backplane.com) Date: Mon, 18 Dec 2000 18:33:20 -0800 (PST) From: Kelly Yancey To: David Magda Cc: Subject: Re: pine4 and cclient ports Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The MAINTAINER tag gives this as an e-mail address so I'm sending this > here. > > This is just an inquiry as to who I should send e-mail to about the > pine4 and cclient ports. I think I've been able to SSL capabilities to > them and am wondering who I should talk to this about. > > I've contacted the pine4-ssl maintainter and he suggested I should > inquire with the cclient maintainer about somehow adding an option to > enable the inclusion of SSL into the build process. (It's rather > straight forward with c-client 4.8 now.) Yes, Nick Sayer has already filed a PR with some patches against, I believe, pine4.21. I must admit that I haven't looked at them yet as I am not very familiar with using pine with SSL and have been too strapped on time to figure it out. However, if you can submit patches against 4.31 and/or point me in the right direction, I'll gladly see to getting the pine4-ssl port back in action. Thanks, Kelly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message