2015-11-03 00:31:35 +01:00
|
|
|
$NetBSD: distinfo,v 1.6 2015/11/02 23:31:46 agc Exp $
|
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.]
2002-05-14 20:47:52 +02:00
|
|
|
|
|
|
|
|
SHA1 (xchrono.shar) = 8cc61b949ff4c1972cfa810831d562d058fa9e2f
|
2005-02-23 20:14:53 +01:00
|
|
|
RMD160 (xchrono.shar) = 8d599f4e594cc0a43c3425841ac8a6670daeaf7e
|
2015-11-03 00:31:35 +01:00
|
|
|
SHA512 (xchrono.shar) = 6df2a7fb9829110d0d8650c32849eadcfe4c974acbdad1f668d45bee88eec79488d615695843d283b82651288eae606b215ddb91e5b6d1a17e0ded201ae84d40
|
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.]
2002-05-14 20:47:52 +02:00
|
|
|
Size (xchrono.shar) = 56292 bytes
|
|
|
|
|
SHA1 (patch-aa) = 59c5946422c0ac76907e1d512dd64b9a1899029d
|
2006-11-29 00:04:54 +01:00
|
|
|
SHA1 (patch-ab) = 73c54769d4c915e1d19f0c94e84731d65a5c5ec4
|
|
|
|
|
SHA1 (patch-ac) = af11c1aeb2cd507896082573756f85522e885bd2
|
