[darcs-users] Newbie questions

Andrew Wagner awagner at uiuc.edu
Mon Feb 14 20:45:04 UTC 2005


On Feb 13, 2005, at 3:26 AM, Erik Bågfors wrote:

> True for readonly protocols (http) but not for read/write ones,
> ssh/sftp for example. Darcs will sftp the files then invoke darcs on
> the remote host.
Thanks Eric!

> I have the same setup, each repo (coming from CVS) has children named 
> 'l10n'
> and one called 'i18n' which all projects share.
> I wrote a script 'initRepo.sh' that checks out these two repositories 
> in the
> root of the darcs repo making my build scripts happy.
> At first I did not think much of it; but as I started to create 
> branches for
> bugfixes that took longer then an hour to implement, I found that the 
> extra
> get's were annoying enough to create a script like this:
>
> #!/bin/bash
> while test ! -d _darcs;
> do
>     cd ..
>     if test `pwd` = '/'; then
>         echo "Failed; no darcs repo found";
>         exit;
>     fi
> done
> echo -n "Working in "
> pwd
> darcs get --partial zander at namlook:/var/www/archives/i18n > /dev/null
>
>
> Its still moderately annoying, though. The changes in those repos 
> don't get
> detected or updated unless you explicitly go into them.
> I would give a lot for a --recursive option on pull/push/whatsnew as 
> well as
> on 'get'.
Thanks Thomas!

So it seems that unlike cvs and svn, which have files in every 
directory of your working copy, darcs stores all of its information in 
one directory at the root of each working copy/repository?

It seems that the script you posted goes up the directory tree until it 
gets to a darcs root and then checks out a new copy of what you have on 
the server?  I've experimented a bit with darcs now, and it seems like 
most all of the commands are smart enough from directories below root 
in the tree.  No so with the "get" command?

> I believe darcs allows you to have darcs repos within other darcs 
> repos,
> which is similar to what you want, but not the same thing. That's not a
> concept I used myself, so I want try to say more about how well it
> might work or not. :)
>
>     Mark
Thanks Mark!

If you have nested darcs repositories, and change something in the 
lower level, you'd have to record basically the same patch at both 
levels, right?  seems like this would be a problem when you go to push 
both levels to another repository and both patches try to modify the 
same file...  Does darcs support nested darcs repositories at all, or 
is this just asking for trouble?  Is knowledge of darcs' current 
behavior for nested repositories collected anywhere?  I couldn't find 
any info on this in the official user manual, and didn't notice 
anything on the wiki.

Thanks for all of your replies, and thanks David, for sharing your 
great software with the world!

Drew Wagner
UIUC ECE Grad Student
Swing Society Photographer
604 W. Nevada #3,  Urbana
Home: (217) 344-5581
Work: (217) 244-6626
AIM: drewillini





More information about the darcs-users mailing list