-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arlie Davis wrote:
> Ok, the rough consensus appears to be:
>
> * Keep changes to svnserve minimal -- only add
> the support to start (and stop!) as a service.
>
> * Have a separate installer.
>
> * All config is stored in the service binary path,
> as a command-line.
>
> The rest is really just nitpicking, and doesn't seem productive.
>
> I actually already have this working, so I'll polish the work and provide
> diffs. This will provide 90% of what people here actually care about, since
> you can use the sc.exe that ships with Windows to install any arbitrary
> service. (Not any arbitrary exe -- the binary still must make use of the
> service API to work as a service. SRVANY.EXE is a dog, and doesn't count.)
>
> These diffs are modest enough (only a single --service arg is added to
> svnserve) that we can probably all agree to commit them. The service
> management part can come later, whether it's command line and/or GUI, etc.
Please do go ahead and submit what you already have.
However, my interpretation of consensus is that svnserve SHOULD have
service install/uninstall capability, and there should NOT be a separate
installer. As you say, though, this can be accomplished in a second
round of changes.
Max.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
iD8DBQFD+526fFNSmcDyxYARAoasAJ0UfhGM7vAZZePXDCcns5RYn2OJ6wCfUgjY
XFbdxEKBlseucaKffQaYiTc=
=MO1E
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 22 00:10:18 2006