Date: Thu, 16 Nov 2000 12:27:36 -0800 From: Nick Sayer <nsayer@sftw.com> To: Ade Lovett <ade@FreeBSD.org> Cc: kbyanc@FreeBSD.org, ports@FreeBSD.org Subject: Re: pine, cclient, linkage.c and SSL Message-ID: <3A144338.CEE03BDD@sftw.com> References: <200011162000.eAGK0g876120@medusa.kfu.com> <20001116141009.A47823@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ade Lovett wrote: > > 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. But then we have twice as many ports. I think the simpler thing maybe is to presume that cclient is ssl-ified unless NO_OPENSSL or some such is defined. This means that if cclient is fixed that all of the cclient dependent ports should have USE_OPENSSL defined and should be fixed to add -lssl -lcrypto unless NO_OPENSSL is defined. How's that sound? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A144338.CEE03BDD>