On Apr 9, 2005, at 5:41 PM, Henrik Thostrup Jensen wrote:
> Hi
>
> I discussed this on #svn, and it was said that I would not like the
> answer to this but I'm gonna try anyway :-).
>
> I have a local fsfs repo, which I want to allow read-only access to
> one of my friends. Unfortunately he does have access to the
> development machine and I cannot run a server on the machine, since it
> is heavily firewalled. The only way I have to export the data is over
> plain http (I have no need for secrecy with the project). I tried
> symlinking to the repo within my .public_html, but I got 301 error
> when trying to check it out. I read the FAQ on the subject, and think
> I understand why I get it, but I cannot change httpd.conf (nor do I
> really want to).
>
> While I can do all sorts of hackish ways to solve the problem
> (post-commit hook or cron job to produce directories/tarballs/emails)
> I would like to able to do checkout over http and update directly from
> it. I don't see why this should be much different than checking out
> from a local read-only fsfs repo.
>
I'm not sure how this could possibly work. By nature, apache httpd can
"deliver" normal files sitting on disk to a client over HTTP. But a
subversion repository doesn't contain normal files -- it's a database
of some type, either BDB, or a custom flatfile database. *Something*
needs to know how to interpret the database and pull files out of it.
In other words, something needs to use libsvn_repos.so and
libsvn_fs.so.
At the moment, that thing is mod_dav_svn. What's the alternative?
What else could it possibly be? What's your proposal?
Also, keep in mind that a client running 'svn checkout http://' is
issuing all sorts of WebDAV/DeltaV commands. It's not just doing a
series of GET requests, it's much more complex than that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 10 15:01:20 2005