1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
todo --------------------------------------------------------------------------
- support for using 32-bit Nethack on 64-bit system, see
http://groups.google.com/group/rec.games.roguelike.nethack/msg/816ab1e67ec2a470
- support for many new features, see Alexis' email from 2005-07-16, Subject:
Hearse updates, Message-ID: <000701c58950$35371b00$1901a8c0@fishtest>
- support for X_MATCHBONES
/m - for each bones file that you upload, it will attempt to download
one of the same level. (i.e. if you upload a level 4 bones file you
will get a different level 4 bones file in exchange). If no bones file
is available for that level, it will revert to the default behaviour
and download a random level instead.
If you wish to support this behaviour for the Unix client, here's how
it works. The filenames of all accepted bones files are stuffed into
a stack. Each time round the download loop, the top filename is
popped off the stack and passed as an argument to the X_MATCHBONES
header, e.g. sending X_MATCHBONES:bonD0.4 will attempt to download
bonD0.4 if possible.
- support for skipping bonescheck
The idea behind the 'bonescheck' phase was that it'd save network
time to send the MD5 of the file and the version info to decide
whether the server will accept it. However, in the common case it
will always ask for the full file to be sent. So simply eliminating
the bonescheck step increases speed by ~25% (probably not so much on
Linux systems since the bones files are bigger, and it's also less
important since you have it set up to run under cron).
If there is a problem with the full bones file, info error messages
will be sent back exactly as they are from the old bonescheck
- switch to reset/ignore timestamp?
/r - resets the 'last uploaded' timestamp (that is, prevents Hearse
attempting to upload old bones files). Included as a workaround for
users who sometimes run into problems with this.
- merge in Crawl-modified version of hearse
- Windows support (see message from Darshan Shaligram from 2003-04-01 in
+project/hearse)
- run evey 15 minutes by default, so you don't miss a bones which is
created then used before the end of the day
- man page
- cron.d
- cron.daily
- code to ensure version in hearse.spec, debian/changelog, hearse match
- simple install instructions for dependencies
- scripts to publish new versions to web page
- bump version: hearse, hearse.spec, debian/changelog
- tell Alexis about new X_HEARSECRC:
echo -n "UNIX-HEARSE $version" | md5sum
- cvs-buildpackage
- move generated files to ../web/dist
- pod2html hearse >! ../web/hearse.html
- pod2html bones-info >! ../web/bones-info.html
- cd ../web/dist
- ln -s hearse_$version.tar.gz hearse-$version.tar.gz
- ln -sf hearse_$version.tar.gz hearse-current.tar.gz
- run-scanpackages
- rpm -tb --sign hearse-$version.tar.gz &&
mv -i /usr/src/rpm/RPMS/noarch/hearse-$version-1.noarch.rpm .
- update web/bones-info
- update version in index.html.m4, gmake
- gmake -C ../web install
- rpm: Is there a way to do interactive configuration at install time?
- rpm: How do Red Hat people do the equivalent of /etc/ppp/ip-up.d?
-------------------------------------------------------------------------------
$Id: Notes,v 1.15 2006-05-30 16:07:50 roderick Exp $
|
