Apology accepted :o)
Any remarks to the following overlooked email?
[snip]
The "bug?" may just be my misunderstanding; here it is, in the form of a
question for the Subversion Dev Team to give a crack at it:
Q: Is it possible for a HOOK (start/pre/post-commit) to access WC
Add/Delete commands (via "svn add" and "svn delete")?
Bkgnd: From this thread conversation with Simon Martel, it appears that
a HOOK *cannot* modify the working copy from which it was instantiated.
Running hook scripts *outside* of a WC "svn commit" command is not a
problem; but based on the WC's "commit" it seems to not execute
ADD/DELETE commands. "svn up" works fine from within a hook script,
though.
In the end, it may not be a "bug" but a limitation of architecture. If
so, then I will just schedule the hook script as a cron-job on the
machine.
Thanks.
[/snip]
Nasser Dassi
Sr. Technical Programmer
=========================================
E: ndassi@141xm.com
=========================================
-----Original Message-----
Subject: Re: Commit hooks malfunctioning...
Simon Comeau Martel <martelsc@videotron.ca> writes:
> > In the latter case, the hook program typically does not inherit the
> > environment of its parent process. For example, a common problem is
> > for the PATH ($PATH or %PATH, in Unix and Windows respectively)
> > environment variable to not be set to its usual value, so that
> > subprograms fail to launch unless invoked via absolute path. If
> > you're having unexpected problems with a hook program, the culprit
> > is probably unusual (or missing) environment variables like PATH.
>
> Well, if 'svn status' run correctly, the problem with 'svn add' can't
> be the PATH...
Ah, I missed that part, sorry.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 21 21:46:27 2005