Not too much, but already tests large parts of sensitive code. Caught a
bug where ,top would use (enter! #f) but enter grabbed the wrong
namespace since it was instantiated in the wrong namespace.
(cherry picked from commit f5e53de4d9)
The problem is that it spits out a warning message on stderr whenever it
can't find a git repository to extract release announcements (from
annotated tags). Resolving this will require some way to (a) tell drdr
to ignore such output, (b) make it run the code with a $GIT_DIR
environment variable set to the git tree, or (c) make it set some
environment variable so the web build will avoid such messages. (I
prefer the first most, and the last least.)
See in-code comments for how this is just a rough feature to be used if
needed (and improved when it becomes necessary). That can just as well
go to the FIXME of using a string constant.
* Add captcha url (unused, yet)
* The second argument to `call/input-url' can be a one-argument function
since the call doesn't send it any headers.
Still needs to be done: check the HTTP response for an error status, and
make it fail as a result (currently it just assumes that any response is
fine, which can change in case of a captcha failure). Then, add a
captcha challenge if one is found, otherwise ignore.
This makes it correspond to the license page we have on downloads that
talks about the "lesser" GPL rather than the "library" one.
Also, change the file name to have a more friendly .txt suffix, and add
some more responsible properties for things in doc/release-notes.
Also get rid of the defunct "chronology" link at the bottom of the
community page. It was a very old (pre-svn/git) leftover from a time
where that was relevant for people who want to participate.
The windows 7 build generated some weird permission issues: the toplevel
directory had a 000 permission as well as all *.exe files. Looks like
it is due to how cygwin translates the permissions of the C:\ drive. A
way to get around this is to have a build directory with pre-set
permissions that cygwin likes, then have the build directory in it.
(This hack might be needed for the other build machine too at some point
in the future.)
Also add /c/Windows/system32 to the PATH, otherwise MS batch files fail
(with obscure errors).
