Date: Sat, 18 Sep 2010 15:09:19 -0700 From: perryh@pluto.rain.com To: kientzle@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Re: ar(1) format_decimal failure is fatal? Message-ID: <4c95388f.vSPICvvA6A5bgvDR%perryh@pluto.rain.com> In-Reply-To: <F56D9CB9-E644-4279-8830-71292C880D9B@freebsd.org> References: <alpine.GSO.1.10.1008281833470.9337@multics.mit.edu> <20100829201050.GA60715@stack.nl> <alpine.GSO.1.10.1009032036310.9337@multics.mit.edu> <F56D9CB9-E644-4279-8830-71292C880D9B@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Kientzle <kientzle@freebsd.org> wrote: > Personally, I wonder if it wouldn't make sense to just always > force the timestamp, uid, and gid to zero .. uid and gid, OK. Timestamp, no. It is not that rare to need to find out which version of some .o is in a particular .a file, usually in connection with debugging some obscure failure. For that matter, aren't there some versions of make(1) that can check whether an archive member is up to date by examining the timestamp in the archive?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4c95388f.vSPICvvA6A5bgvDR%perryh>