From owner-freebsd-ports Mon Nov 3 17:42:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23015 for ports-outgoing; Mon, 3 Nov 1997 17:42:39 -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 RAA23009 for ; Mon, 3 Nov 1997 17:42:37 -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 RAA04376; Mon, 3 Nov 1997 17:42:20 -0800 (PST) To: Ian Vaudrey cc: "'ports@freebsd.org'" Subject: Re: Ranlib In-reply-to: Your message of "Mon, 03 Nov 1997 23:53:46 GMT." <01BCE8B3.D1F95660@nemkoltd.nildram.co.uk> Date: Mon, 03 Nov 1997 17:42:20 -0800 Message-ID: <4372.878607740@time.cdrom.com> From: "Jordan K. Hubbard" 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. > BTW, the refusal of pkg_delete to delete changed files is something that > must've seemed a real good idea at the time, but in practice is a pain in > the rear. This is the second time it's bitten me, there should be a way to > override it. I suppose I could put in an override flag or something, but this feature was actually specifically requested by the user base - it didn't use to be this way. :) > P.S. So *does* the @exec ranlib line serve any purpose? You of all people > will know. I'm not sure if this is still true with the GNU loader, but in the past even copying a library would generate "symbol table out of date" warnings if the internal symbol table had an older creation date than the library itself. Jordan