-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mark Phippard wrote:
> I apologize in advance if this has been already discussed, but why
> wouldn't you put the "service maintenance" options (create, update,
> delete, list) in a separate executable, like svnservice.exe or something?
> And just limit the changes to svnserve.exe to those needed to actually run
> as a service? That seems like it would be a lot cleaner and greatly
> reduce the changes need to svnserve.exe itself. I do not like the idea of
> all of those command line options being added to svnserve.exe.
Since the infrastructure to actually run as a service must, by
definition, go into svnserve.exe, I would strongly prefer to see the
service maintenance code go there too. It's an obvious place for users
searching for the functionality to look, and avoids yet-another-binary.
It also neatly avoids the need to specify the path to svnserve itself to
the service installer, since the process can just get its own filename.
Max.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
iD8DBQFD+4ljfFNSmcDyxYARAtP+AJ9/tdvSwRD7VGYIQnIULN+DmlB2mQCgxmUz
Sm1JGE0IUtv88JbrKpPvN3w=
=cyrg
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 21 22:43:39 2006