Date: Mon, 03 Nov 1997 17:42:20 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Ian Vaudrey <i.vaudrey@cableinet.co.uk> Cc: "'ports@freebsd.org'" <ports@freebsd.org> Subject: Re: Ranlib Message-ID: <4372.878607740@time.cdrom.com> In-Reply-To: Your message of "Mon, 03 Nov 1997 23:53:46 GMT." <01BCE8B3.D1F95660@nemkoltd.nildram.co.uk>
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. > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4372.878607740>