On Jan 23, 2005, at 9:08 PM, JC Hearn wrote:
> You are right to suggest that this is not a shortcoming of Subversion.
>
> However, the developer community which has grown up around Subversion
> seems
> to have made an incorrect assumption (unless I am completely
> misreading the
> various documentations, which I will allow as a very real possibility.)
>
> That incorrect assumption seems to be that it is OK to access the
> repository
> via HTTP, SSH or FTP, but the working copy MUST be accessed via the
> local
> file system. Why not allow the same access to the working copy? Why
> force
> the user to open additional security issues (such as those associated
> with
> SAMBA)? Or even better, why not have an API to allow the user to move
> files
> from one place to another on the web server?
That "incorrect assumption" is one of the *fundamental* design concepts
that Subversion is built around. Subversion was never intended to be
used in the manner in which you describe.
That's not to say that it can't be done, but doing what you want is
like trying to cut a steak with a spaceship.
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 24 06:01:32 2005