Debian Codegraph @

Notes

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