From owner-cvs-all Sat Jan 15 20:19: 9 2000 Delivered-To: cvs-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id E0C1B14E6C; Sat, 15 Jan 2000 20:19:06 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D58331CD5E6; Sat, 15 Jan 2000 20:19:06 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 15 Jan 2000 20:19:06 -0800 (PST) From: Kris Kennaway To: Brian Fundakowski Feldman Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/secure/lib Makefile src/secure/usr.bin Makefile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On Sat, 15 Jan 2000, Brian Fundakowski Feldman wrote: > Well, you have to realize that we all have a responsibility to not break > things. Committing a library with significant missing functionality, > having the same name as a preceding port _with_ that functionality, is > very bad. It breaks our ports. I know you're the maintainer, but you > have to really think about the responsibility of keeping things working. Ever heard of LD_LIBRARY_PATH? There's no reason you have to stop using your ports-built openssl until the in-system is working to your satisfaction. Getting reports of other things which might be broken with the library is IMO much more important than the temporary inconvenience of missing functionality, given the approaching release and the above workaround. I want to hear of any non-RSA related problems with openssl, which means getting widespread testing now. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message