[pacman-dev] makepkg3 improvements (for pacman-3.1)
aaronmgriffin at gmail.com
Wed Sep 19 11:42:35 EDT 2007
On 9/19/07, Roman Kyrylych <roman.kyrylych at gmail.com> wrote:
> 2007/9/19, Aaron Griffin <aaronmgriffin at gmail.com>:
> > On 9/19/07, Roman Kyrylych <roman.kyrylych at gmail.com> wrote:
> > > 2007/9/19, Aaron Griffin <aaronmgriffin at gmail.com>:
> > > > Carving my way through some old emails....
> > > >
> > > > How does this sound for a sanity check while we do this conversion:
> > > > If build/install date start with a non-digit, use old code, otherwise
> > > > asssume it's an epoch?
> > >
> > > What do you mean by epoch?
> > > ISO 8601 date format YYYY-MM-DDThh:mm:ssTZD
> > > (e.g. 1997-07-16T19:20:30+01:00)
> > > or just the Unix timestamp (number of seconds since 1970)?
> > http://en.wikipedia.org/wiki/Unix_epoch
> "The Unix epoch is the time 00:00:00 UTC on January 1, 1970". :-P
> I knew this before, nothing new.
> I asked about the string format used to represent the time.
> "For brevity, the remainder of this section will use ISO 8601 date
> format, in which the Unix epoch is 1970-01-01T00:00:00Z."
> So? ;-)
"it is the number of seconds elapsed since midnight UTC of January 1, 1970"
"number of seconds" is the operative term. It is not a string format,
it is a number.
Using _any_ string format will cause problems in the future.
As an aside though, the strptime parsing of the old-format dates in
the patch on my working branch also gives us timezone adjustments.
More information about the pacman-dev