From owner-freebsd-ports Thu Nov 16 12:10:15 2000 Delivered-To: freebsd-ports@freebsd.org Received: from hub.lovett.com (hub.lovett.com [216.60.121.161]) by hub.freebsd.org (Postfix) with ESMTP id 80C8D37B479; Thu, 16 Nov 2000 12:10:12 -0800 (PST) Received: from ade by hub.lovett.com with local (Exim 3.16 #1) id 13wVMH-000CRv-00; Thu, 16 Nov 2000 14:10:09 -0600 Date: Thu, 16 Nov 2000 14:10:09 -0600 From: Ade Lovett To: Nick Sayer Cc: kbyanc@FreeBSD.org, ports@FreeBSD.org Subject: Re: pine, cclient, linkage.c and SSL Message-ID: <20001116141009.A47823@FreeBSD.org> References: <200011162000.eAGK0g876120@medusa.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011162000.eAGK0g876120@medusa.kfu.com>; from nsayer@quack.kfu.com on Thu, Nov 16, 2000 at 12:00:42PM -0800 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 16, 2000 at 12:00:42PM -0800, Nick Sayer wrote: > The problem is that ports that are dependent on cclient may now > unknowingly need to add -lssl -lcrypto in order to link. Or perhaps > not (if the user compiled cclient with -DADDSSL=no). > > What should be done about this whole situation? IMO.. add support for SSL to mail/cclient.. create a satellite port mail/cclient-ssl that simply turns this flag on, then depend on mail/cclient if you don't want SSL, and mail/cclient-ssl if you do. -aDe -- Ade Lovett, Austin, TX. ade@FreeBSD.org FreeBSD: The Power to Serve http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message