From owner-freebsd-ports  Tue Nov  4 02:07:07 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA00461
          for ports-outgoing; Tue, 4 Nov 1997 02:07:07 -0800 (PST)
          (envelope-from owner-freebsd-ports)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA00446
          for <ports@freebsd.org>; Tue, 4 Nov 1997 02:06:59 -0800 (PST)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id CAA08023; Tue, 4 Nov 1997 02:06:41 -0800 (PST)
To: asami@cs.berkeley.edu (Satoshi Asami)
cc: i.vaudrey@cableinet.co.uk, ports@freebsd.org
Subject: Re: Ranlib 
In-reply-to: Your message of "Mon, 03 Nov 1997 22:29:17 PST."
             <199711040629.WAA15843@silvia.HIP.Berkeley.EDU> 
Date: Tue, 04 Nov 1997 02:06:41 -0800
Message-ID: <8020.878638001@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
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.

Ahhhh.  Now that's different!  He said that the @exec line was being
run by pkg_delete, not that it was fooling the md5 check into failing.
Yeah, I can see how that would happen.

Hmmmm.  Is the ranlib even necessary with the GNU loader?  If not, why
not just take that out?

					Jordan