[darcs-users] Re: Darcs and a single developer working on multiple workstations

Daan Leijen daan at cs.uu.nl
Wed Mar 23 20:04:53 UTC 2005

On Wed, Mar 23, 2005 at 08:45:20AM -0800, Steven E. Harris wrote:

>>Michael G Schwern <schwern at pobox.com> writes:
>>>darcs works over plain, dumb HTTP and also SSH (and probably FTP).
>>>So what you'd do is put your main darcs repository up on your
>>>FTP/HTTP site.
>>I've been struggling with this same goal, and regret to note that it's
>>just not this simple for anything but read-only tracking of a public
>>"master" repository.
Despite all the solutions given, it still seems that it is not very easy 
to have a public
repository: all solutions require things like "scp" and/or "darcs 
send/apply" via email.

I think it would be a great selling point if darcs could push/pull to 
any ssh accessible
site even when darcs is not installed. It is surely possible, here is a 
slow but working

1) lock and scp the entire repo from the server to the client
2) do darcs push locally
3) scp everything back and unlock

Maybe the above solution is too expensive, but one can probably optimize 
the needed
traffic on the wire. This would make darcs *much* more usable as any old 
http site could
serve as a darcs server -- no darcs installation required and no admin 
Of course, if it is too much work to implement, this might not be a good 
idea, but otherwise,
it would be a major selling point for darcs in favor of other SCM's  
(but don't worry,
I am already convinced :)

-- Daan Leijen.

>>In order to push changes back to this master repository, that
>>repository must sit on a host that has darcs available. That poses a
>>problem for those who have some public storage space between two
>>disconnected workspaces (say, home, work, and an ISP in between), but
>>do not have darcs available on that public host.
>wouldn't 'darcs send' work well for this?  I have never used it
>personally so someone correct me if I am wrong.  I'm imagining this
>scenario, and this is all complete conjecture.
>    home: darcs master repository, darcs, incoming email 
>    work: darcs working repository, darcs, outgoing email
>    ISP : darcs master read-only repository, no darcs, webserver
>The process would be something like this:
>    home -> ISP : sync the home master repositor to an ISP read-only
>                  repository via rscync/scp/ftp/other periodically.
>                  Here's where a post-record trigger would be nice
>    ISP -> work : darcs pull
>    work -> home: darcs send --to=home-email-address
>                  - on the home side, procmail pics up the sent patch
>                    bundle and feeds it to some script.
>                  - the script applies the patch to the home darcs
>                    repository, and then ISP repository with the home
>                    repository.
>Its a bit convoluted but it might work.
>Jeremy Hinegardner                              jeremy at hinegardner.org 
>darcs-users mailing list
>darcs-users at darcs.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osuosl.org/pipermail/darcs-users/attachments/20050323/97e25c61/attachment.htm 

More information about the darcs-users mailing list