Ken Moffat wrote: > 2. How did you decide on that date and time ? Um. Yeah. I looked at what "ls -l" with no special configuration was telling me, and picked a time that was comfortably earlier than the mtime on aclocal.m4.
This is probably completely unusable for people in other timezones; I didn't even think about the fact that I was using localtime. :-) > In a just untarred > kbd tree, with configure touched to simulate an update, in UTC+1 > I get > > root in chroot /building/kbd-1.15.3# ls -l --time-style=long-iso \ > configure* aclocal.m4 > -rw-r--r-- 1 ken 500 36173 2011-05-07 21:32 aclocal.m4 > -rwxr-xr-x 1 ken 500 263199 2012-06-07 00:08 configure > -rw-r--r-- 1 ken 500 2099 2011-05-14 22:37 configure.ac Yeah, configure.ac needs to be moved back about seven days, one hour, and five minutes, or so. (Plus a bit to be safe.) We could do "second since the epoch", by preceding an integer with an @ character. That's at least unambiguous. Or we could add a timezone, with a string like '2011-05-07 21:00 +0100' (or whatever the equivalent is at UTC+0). > Your touch works, but I'd like to understand why, and therefore to > be sure it will also work for people in all timezones (apparently, a > range of -10 to +14, or from -12 if the military timezones actually > exist). It shouldn't work in all cases. :-)
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
