CVS log for pkgsrc/time/xchrono/distinfo

Up to [cvs.NetBSD.org] / pkgsrc / time / xchrono

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

time: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

time: Remove SHA1 hashes for distfiles

Add SHA512 digests for distfiles for time category

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.

Quieten some more warnings which gcc4 gripes about

Add RMD160 checksums.

Use "Australia/Sydney" instead of "Australia/Queensland" for the
"sydney" timezone, otherwise Sydney suddenly misses out on daylight
savings time.

Merge from pkgsrc-current to buildlink2 branch.

file distinfo was added on branch buildlink2 on 2002-06-23 19:02:59 +0000

make this go on alpha

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.]

Initial revision