> So you would prefer to duplicate effort by having a separate service
> installer? It's a Windows-specific feature, so make it work like every
> other Windows service and have the ability to install and uninstall
> itself. Don't alienate the Windows users by making it work differently
> than what they expect it to do
Other than OS/400, I am exclusively a Windows user. I certainly do not
have any goals to alienate anyone, and I am just providing comments anyway.
I have no opposition to the proposal.
Maybe we use vastly different software, but virtually every Windows service
I have ever used was installed via their InstallShield-type routine. Like
I said before, for all I know these services have all of the service
management code in the same executable and the install routines are just
invoking it. I do not know. If everyone thinks the service management
code belongs in svnserve I do not have any objections. I just thought it
would be simpler and more likely to pass code review if it wasn't. I have
no problem being wrong.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
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:15:43 2006