automatic disable won't cause a warning

*_r() functions as they're not needed (and if fact mess things up for us).
Brought to our attention by the friendly Troels Walsted Hansen in bug report
#696217.

code as this makes compiler warnings. We *should* fix the code to deal with
the return codes instead...

lingering POST-stuff that confuses GET requests. Juan F. Codagnone reported
this problem in bug report #653859.

compiler, mentioned by Andi Jahja

the recent libcurl changes.

looks like.

when SIZE is used on the file while being in BINARY mode. To work
around that (stupid) behavior, we attempt to parse the RETR response
even if the SIZE returned size zero.

Debugging help from Salvatore Sorrentino on February 26, 2003.

include size in the 150-reply

function, as this could easily end up looping for a very long time (more or
less until the whole transfer was done) and no library-using app would want
that.

Found thanks to a report by Kyle Sallee.

header is used, we must wait for a 100-code (or timeout), before we send the
data. The timeout is merely 1000 ms at this point. We may have reason to set
a longer timeout in the future.

than 5 could cause a segfault.

so we now remove everything matching "build-*" when the script starts.

people how to get even more details shown

even better (also based on input from Martin).