Re: Program to start long running hooks in Windows for Subversion >= 1.3

Hi Ryan,

> That bug says it is "resolved" and "works for me."

Correct, apparently it works fine on Linux, which seemed to
be the o/s used by the person who replied to the bug report.

> Are you saying it still does not work?

Perhaps a better way of saying it is I've yet to see a way to
spawn processes in Windows using standard commands
whilst ensuring the stdout and stderr streams where closed.

In a nutshell, svn < 1.3.0 running "start /b <cmd>" worked in
spawning post commit hooks, but in svn >= 1.3.0 it doesn't.

The difference seems to be with Linux you just have to place
an ampersand on the end of a command to spawn it, whereas
in Windows you have to use another command, so the redirection
rules may be changed (not sure), but I tried many combinations
and couldn't get it any to work.

There is probably another way to achieve this using dos,
but I couldn't find it, so rolled my own solution.

> Does the bug need to be reopened?

If someone can demonstrate how to do it in Windows,
then no, otherwise perhaps it should be. If it does get
resolved, it's probably a faq worthy entry.

> Are you using Subversion 1.3.2?

Yes

peace
si

p.s. There do seem to be differences between the Windows
and Linux implementation of Subversion which are not detailed
in the documentation. For example, environment variables are
retained in hooks in Windows, but not in Linux.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 12 04:20:09 2006