Problems found with mismatching existing digests for:
distfiles/asclock-classic-1.0.tar.gz
distfiles/asclock-gtk-2.1.10beta.tar.gz
distfiles/asclock-xlib-2.0.11.tar.gz
distfiles/emiclock-2.0.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
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.]