I am working for an organization that has imposed a very odd svn/
development setup. Basically, we all have to use svn (update, commit
etc), but we can't work with our own working copies (i.e. develop and
test). Every change we make to the code (even a color change in a css
file!) we have to commit it, then the repository does a post-commit
hook script which updates the development server, so we can see our
changes. We are already up to 800 revisions and most of the messages
in svn log are blank or say things like "changed stuff".
Because I am at the bottom of the totem-pole in this company, all I
can do is accept the wonky situation (I have tried to explain what is
wrong with it and how to improve it, to no avail). Anyways, I needed
to just talk about it ;) but the main problem now, is that the post-
commit hook is not adding new directories, only new files to the
development server. For instance, if the directory already exists,
then new files are added to it. But if it does not exist, then
nothing is created (directory or files).
I have checked to make sure (in my working copy) that the directories
are under version control, and they are.
Here is the script they are using:
REPOS="$1"
REV="$2"
DELTADIR=`/usr/bin/svnlook dirs-changed -r "$REV" "$REPOS"`
/usr/bin/svn update -N /home/devel/$DELTADIR
-- David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Sep 3 19:33:09 2006