Oy, there are so many misconceptions here, I don't know where to start!
On Jan 17, 2005, at 12:54 PM, Dassi, Nasser wrote:
> ssible working copy does not actually update the working copy.
> [example of WebDAV Only]
> 1. I have a working copy at "d:\htdocs\webdav\" of a Repository.
Meaning, you did an 'svn checkout' of some repository, and that created
a working at d:\htdocs\webdav, correct? It's a normal working copy,
complete with .svn/ areas, right?
> 2. I make the directory WebDAV-accessible via Apache2 + mod_dav.
Okay, so now you can mount this working-copy dir as a network share.
> 3. I WebDAV-update a file.
By "WebDAV-update", you mean, "did a PUT"? That is, you changed a file
in the mounted DAV share? If so, then this is just like editing a file
in the working copy with an editor, right? You have a local
> 4. The working copy file is up-to-date.
I think you have a different definition of "up-to-date" than the rest
of us. Up-to-date compared to what? Certainly not compared to the
repository. The file in the working copy has been edited. It's
"newer" than what's in the repository.
> 5. The SVN Repository is not changed (obviously, bc Autoversioning
> is off).
The repository isn't changed, because you never ran "svn commit". It
has *nothing to do* with autoversioning.
> [example of WebDAV, SVN, Autoversioning]
> 1. I have a working copy at "d:\htdocs\webdav\" of a Repository
Okay, same as before.
> 2. I make the directory WebDAV-accessible via Apache2 + mod_dav_svn.
This makes no sense to me at all. The mod_dav_svn "autoversioning"
feature makes a *repository* understand generic PUT requests, rather
than complex DeltaV requests. It has nothing to do with exporting a
working copy. If you tried to make a working copy available like this:
... then I would expect endless errors. That set up expects
d:\htdocs\webdav to be a *repository*, not a working copy. I would
expect constant errors about "not being able to find a repository" any
time you accessed the URL. Is this what you did?
Or, do you simply mean that you made the *repository* (not the working
copy) available through mod_dav_svn? Will you please show us exactly
what you did, and stop describing it anecdotally?
> 3. I WebDAV-update a file.
> 4. The working copy file is *not* up-to-date.
> 5. The SVN Repository *is* changed (bc Autoversioning is ON).
Nothing will cause a working copy to update except the 'svn update'
> ... Am I the only person to experience this? Is there a way to have
> the working copy _share_ updates with SVNAutoversioning so *both* WC +
> Repo are updated simultaneously?
I'm guessing here. It sounds like what you want is to be able to
change a repository through Autoversioning PUT commands, and then have
some other working copy (somewhere else) automatically receive those
If so, then that's a very common thing, and it has nothing to do with
autoversioning at all. Just install a post-commit hook script that
runs 'svn up' on the working copy. I do that myself, as a way of
keeping my ~/public_html/ website up-to-date after every commit I make.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jan 17 20:24:25 2005