From owner-freebsd-ports  Mon Nov  3 22:32:20 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA15590
          for ports-outgoing; Mon, 3 Nov 1997 22:32:20 -0800 (PST)
          (envelope-from owner-freebsd-ports)
Received: from silvia.HIP.Berkeley.EDU (wck-ca14-30.ix.netcom.com [207.92.174.94])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA15526
          for <ports@freebsd.org>; Mon, 3 Nov 1997 22:32:00 -0800 (PST)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id WAA15843; Mon, 3 Nov 1997 22:29:17 -0800 (PST)
Date: Mon, 3 Nov 1997 22:29:17 -0800 (PST)
Message-Id: <199711040629.WAA15843@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: i.vaudrey@cableinet.co.uk, ports@freebsd.org
In-reply-to: <4372.878607740@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: Ranlib
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * > I can reproduce the problem with at least one existing port, libmalloc-1.18,
 * > I haven't tried any others but if I'm right about the cause it'll happen
 * > with any port that has an @exec ranlib line in the PLIST.
 * 
 * I'll take a look at it.  Like I said, @exec lines aren't even supposed
 * to be _run_ by pkg_delete so this would be a very peculiar situation
 * of so.

No, he's right.  "@exec ranlib" is run by pkg_add, and that changes
the md5 checksum, which causes pkg_delete to choke.

Satoshi