From owner-freebsd-ports  Sun Jun  4 01:26:58 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id BAA03095
          for ports-outgoing; Sun, 4 Jun 1995 01:26:58 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA03043
          for <freebsd-ports@FreeBSD.org>; Sun, 4 Jun 1995 01:26:41 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id BAA02028; Sun, 4 Jun 1995 01:26:28 -0700
Date: Sun, 4 Jun 1995 01:26:28 -0700
Message-Id: <199506040826.BAA02028@silvia.HIP.Berkeley.EDU>
To: joerg_wunsch@uriah.heep.sax.de
CC: freebsd-ports@FreeBSD.org
In-reply-to: <199506040622.IAA25865@uriah.heep.sax.de> (message from J Wunsch on Sun, 4 Jun 1995 08:22:09 +0200 (MET DST))
Subject: elm and descrypt (Re: UNIX crypt() source - the problem solved (fwd))
From: asami@CS.Berkeley.EDU (Satoshi Asami)
Sender: ports-owner@FreeBSD.org
Precedence: bulk

According to Joerg:

 * Hmm, this reminds me of another pitfall.  I don't know about Pine/
 * IMAPD, but Elm requires to be linked against -ldescrypt, in order to
 * get its internal message {en,de}cryption correct.
 * 
 * Satoshi, the configure script in our port should be aware of this, and
 * it might warn the user about the disfunctional encryption if there's
 * no such thing like -ldescrypt available.  (I don't know who's the
 * maintainer of the elm port.)

Something like this?

post-configure:
	if ! ldconfig | grep -q descrypt; then
	  echo "Seems like you don't have the DES crypt library (libdescrypt)."
	  echo "The internal message {en,de}cryption may be incorrect."
	fi

Satoshi