I think I'm ready to check in ra_svn. It's only minimally useful at
the moment (because it only supports anonymous authentication), but
it's a good starting point.
I'd prefer not to break the windows build. The client code might
conceivably build and work, but I'm clueless on how to write the
equivalent of a daemon process on Windows. (The socket stuff seems
pretty simple, but the other trappings of a daemon process seem
difficult. on Unix, at startup you background, dissociate from the
controlling tty, change dirs to "/", and ditch stdin/stdout/stderr; I
also need to fork a process to handle each connection. Alternatively,
I could run out of inetd, but that's equally Windows-unfriendly.)
I'm guessing that without the dsp generator in place, checking in new
code won't hurt the Windows build because the .dsp files won't have
changed. But it looks like we're pretty close to have a dsp
generator, at which point the new directives in build.conf are likely
to get into people's way.
What should I do here? In the long term, of course, both the client
and server should operate on Windows, but I'll need some help on that
since I lack a Windows development environment.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 2 04:27:32 2002