Date: Tue, 04 Nov 1997 02:06:41 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: i.vaudrey@cableinet.co.uk, ports@freebsd.org Subject: Re: Ranlib Message-ID: <8020.878638001@time.cdrom.com> In-Reply-To: Your message of "Mon, 03 Nov 1997 22:29:17 PST." <199711040629.WAA15843@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
> * > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8020.878638001>