[DarcsWiki]$ time darcs put --debug cho:public_html/
    Creating repository
    Beginning identifying repository .
    Done identifying repository .
    ssh cho darcs initialize --repodir='public_html' --darcs-2 --hashed
    [...]

I expected this to initialize a directory cho:public_html/DarcsWiki.
Instead it just used cho:public_html -- i.e. it did not check if
public_html is an existing directory.

IMO the put logic for the destination should be the same as the get
logic.  (Maybe it is, and I just need more coffee.)

Doesn't darcs get foo bar/ initialise a repository bar?

I always get confused about what darcs put does (perhaps the help just needs to
be even more explicit).

Marking wont-fix for now.

On Thu, Apr 09, 2009 at 11:40:25AM -0000, Eric Kow wrote:
> Doesn't darcs get foo bar/ initialise a repository bar?

Sorry, the case is where d/ (or in your case, bar/) already exists.
As it turns out, "darcs get" has the same issue if you supply two
arguments.  I'm not sure what the behaviour should be.

If darcs get/put is conceptually like a recursive cp(1), then
attempting to copy x to y/ where y/ already exists, ought to be the
same as trying to copy x to y/x.

$ with-temp-dir
with-temp-dir: entering directory `/tmp/with-temp-dir.mKisaH'
This directory will be deleted when you exit.
$ darcs init --repo r
$ mkdir d
$ darcs get r d/

darcs failed:  Directory or file named 'd/' already exists.
$ cd d/
$ darcs get ../r
Finished getting.
$ cd ..
$ mkdir e
$ darcs put --repo r e
darcs: /tmp/with-temp-dir.mKisaH/e: createDirectory: already exists (File exists)

$ darcs put --repo r e/r
No patches were selected to put. Nothing to be done.
$