Sorry if I'm all over the map here.
I've come to the discovery that I need to add the "svn:mime-type" property to
all of the PDF documents in all my repositories in order to get those documents
treated as binary data when served from Apache. From here
(http://subversion.apache.org/faq.html#auto-props), I discover that there is no
easy way to do this: "to set properties on all files already in the repository,
you'll need to do it the hard way. All you can do is run svn propset on every
file (in a working copy), and then svn commit.".
So, I'm left with the task of looping over all the repositories, checking them
out, looping over all the PDFs, and invoking "svn propset" from the command
line. Which isn't great, but whatever. I guess I can do that.
The script itself is easy to write. It's the idea of waiting for all of that to
run. And then adding a similar mechanism to the "post-commit" trigger to invoke
that behavior whenever someone makes a change to the repository. And, yes, I
could try to educate folks on keeping up with these properties on their end, but
I *know* it'll never work 100% of the time.
Then I tried something. I tried adding a property to a file from the
TortoiseSVN Repo-Browser. This was a property on a file that I DID NOT have
checked out locally to my computer. It, of course, worked like a charm. And,
it worked quickly (meaning that it obviously did not check out the whole folder
in the background).
How? And, more to the point, how can I tap into that and script it? Knowing
that TortoiseSVN is able to do something that the SVN command line client thinks
is impossible is really eating at me. I need to complete this task, but want to
really explore all avenues before I do it the hard way. What am I missing here?
How is TortoiseSVN able to perform an operation that I can't accomplish via the
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-11-03 14:45:09 CET