Date: Thu, 16 Nov 2000 12:00:42 -0800 (PST) From: Nick Sayer <nsayer@quack.kfu.com> To: kbyanc@FreeBSD.org, ports@FreeBSD.org Subject: pine, cclient, linkage.c and SSL Message-ID: <200011162000.eAGK0g876120@medusa.kfu.com>
next in thread | raw e-mail | index | archive | help
I once upon a time made the pine4+ssl port that added the ability to
make mailbox names like {host/imap/ssl}INBOX work. With the separation
of libc-client into its own port, the pine+SSL port is now broken.
That's fine. I'm working out the fixes to the cclient port that will
add SSL there so that all of the consumers of cclient can use syntax
like {host/imap/ssl}INBOX and just work.
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?
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?200011162000.eAGK0g876120>