Call it a bug if you like but I like the env being intact as is :)
I do understand that by keeping propagating the env from Windows,
that problems can occur from mis config'd systems,etc... (some thing
common in batch queuing systems).
However it made my life easier.
If you want to confirm, create a post hook with;
set >> c:\temp\foo.txt
And for the record, I would rather have had the repo server on Unix
however it was already in place when I started at my current gig.
On Aug 5, 2007, at 7:19 PM, Ryan Schmidt wrote:
> On Aug 5, 2007, at 11:08, Brian Krusic wrote:
>> On Aug 5, 2007, at 7:21 AM, Brian E. Fox wrote:
>>> On windows, the hooks are executed with no env set. This means
>>> you need to define any vars that are expected inside you bat
>>> file. It is also why something may work when you run it manually
>>> but not as a hook.
>> The problem wasn't the env however I ran "set" and redirected it
>> to a file in a hook script and found the complete env in Windows
>> was set contrary to the docs.
> Yes, the env is empty on UNIX-like systems, but I've heard it
> reported here before that on Windows the env is not empty. I'd call
> that a bug; Subversion should empty the env on Windows systems too,
> to be consistent, and since the Book says the env is empty for
> security reasons.
> Can we agree that this is a bug? I couldn't find one filed in the
> issue tracker.
>> The actual problem was that Apache is normally run as the SYSTEM
>> user so I changed it to run as a user having access privs to the
>> repo and it worked.
> I'm glad you got the problem resolved.
Received on Mon Aug 6 06:06:53 2007