> I don't know, I really like the idea of pushing via sftp. It is inherently
> less efficient in terms of bandwidth usage, since you have to write
> complete files. Certainly allowing pushes to a repository that has both
> pristine cache and working directory sounds like a very bad idea --
(Speaking about that: what about an option to have repositories
without a working directory?)
> you'd have to send over the network the entire contents of your code
> tree two times at the minimum,
I'm not following here. Why do you need to copy files that you're not
touching? I don't see why going over FTP or sftp[1] should be worse than
over NFS.
> At this point, perhaps you're thinking that we could require rsync to be
> installed on the server instead of darcs,
(Nod.)
> but at this point, I'd suggest you just install darcshive.
(Nod, nod.)
Juliusz
[1] Or HTTP, in fact, using PUT and a couple of weird tricks (not
necessarily portable across servers) to get a lock reliably.
|
