On Fri, 16 Jan 2015, John Meissen wrote:
> Why would you expect the timestamp on a directory to change without
> changing anything in the directory?
John,
Guess I was not sufficiently clear. All files in ./sqlite/ have today's
date; none display a timestamp. That directory was created a couple of
months ago and the previous upgrade (to 3.0.7.4) had no issues. That's
before the system was rebooted.
In that directory is the source file, sqlite-src-3080800.zip and when I
look at the files within that (using 'unzip -v sqlite-src-3080800/') they
all have a date/time like this:
Makefile.in
267 Defl:N 190 29% 01-16-2015 05:47 3fe38957
sqlite-src-3080800/sqlite3.pc.in
That's when the .zip file was built.
I unzip it, then tar it:
tar cvf sqlite-src-3080800.tar sqlite-src-3080800/
and when I look at the tarball (say at 13:08) with 'tar tvf
sqlite-src-3080800.tar' I see:
-rw-r--r-- rshepard/users 267 2015-01-16 20:47
- sqlite-src-3080800/sqlite3.pc.in
What I'm trying to learn is where the additional 15 hours was put in.
Normally I could not care less about time stamps except that the tarball
will not build with the script because of the differences in time.
Is this more clear?
Rich
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
