Initial import of xchrono, a multi-timezoned X11 clock, into the NetBSD
authoragc <agc>
Tue, 14 May 2002 18:47:52 +0000 (18:47 +0000)
committeragc <agc>
Tue, 14 May 2002 18:47:52 +0000 (18:47 +0000)
commit8db78f2f05faa88b1d5acfd159209933a07ee421
tree1663813d4ada78cebd9190fda12b4732e2e93829
parent73388a83b595b524916188dfc05848851459142e
Initial import of xchrono, a multi-timezoned X11 clock, into the NetBSD
packages collection.

Xchrono is a multi-timezone, multi-face clock program for X Windows.
Several cities have been compiled into xchrono, and can be invoked with
command-line arguments, xchrono -help gives:

Usage: xchrono [-analog] [-bw <pixels>] [-digital]
       [-fg <color>] [-bg <color>] [-hd <color>]
       [-hl <color>] [-bd <color>]
       [-fn <font_name>] [-help] [-padding <pixels>]
       [-rv] [-update <seconds>] [-display displayname]
       [-geometry geom]
       [-width clockWidth] [-height clockHeight] [-local localName]
       [-boston] [-newyork] [-chicago] [-denver] [-la]
       [-hawaii] [-tokyo] [-sydney] [-london]
       [-paris] [-frankfurt] [-rio]

OK, OK, Hawaii isn't a city, but you get the point. The timezones used
are taken from tztab in the SYSV case, and from /usr/lib/zoneinfo
otherwise, and as such may or may not be correct (the TZ variable
definitions or the city->timezone mappings).

The -local <localName> option causes a clock labeled with <localName>
using the value of TZ at startup as it's timezone.  In addition, a GMT
clock always appears.

[Requested by groo, who has enough trouble with one timezone, so why he
wants more is beyond me.]
time/xchrono/DESCR [new file with mode: 0644]
time/xchrono/Makefile [new file with mode: 0644]
time/xchrono/PLIST [new file with mode: 0644]
time/xchrono/distinfo [new file with mode: 0644]
time/xchrono/patches/patch-aa [new file with mode: 0644]