On Fri, Sep 28, 2007 at 01:26:58AM -0400, Aaron Griffin wrote:
commit 47622eef4dd8fd86a0aa0e3ebdb7b33f7c9d6804 Author: Aaron Griffin <aaronmgriffin@gmail.com> Date: Wed Sep 19 00:21:56 2007 -0500
Support for localized times in metadata
Packages and DBs now support using the UNIX epoch (seconds since Jan 1, 1970) for use in builddate and installdate. This will only affect newly built packages. Old existing packages with the text format are still supported, but this is deprecated.
In the case of removal of text time support, this code will fail gracefully, returning the start of the epoch for broken packages.
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
What about packages built with 3.0 that are installed / upgraded with 3.1 ? Apparently, for these packages, the build time isn't copied over to the local database. But the install date is generated and stored, in UNIX epoch. I am not saying this behavior is bad or anything, I rather just want to check this is the intended behavior :)