CODEWITHSUNDEEP
mercurial
pachanga
pachanga

Reputation: 3073

Cloning mercurial repo to the remote host

Mercurial supports push-style cloning of repositories to remote hosts, however newly cloned repositories don't contain working copies. Is there any 'hidden' option to make mercurial call update upon these cloned repos?

Here is an example:

1) hg init hello

2) hg clone hello ssh://somehost/hello

ssh://somehost/hello only contains .hg directory and I have to execute the following command in the shell in order to fill the working copy:

3) ssh somehost 'cd hello && hg update'

Is there any way to avoid step 3) ?

Upvotes: 13

Views: 5019

Answers (3)

Nick Zalutskiy
Nick Zalutskiy

Reputation: 15440

You can create a hook on the receiving side. Add the following section to your repo/.hg/hgrc

[hooks]
changegroup = hg update

That should do it. Note that hooks are not cloned.

Upvotes: 13

tehfink
tehfink

Reputation: 477

i have the same problem, and unfortunately there is no simple solution to avoid step 3. mercurial doesn't check out the working copy remotely as "git clone" does, so you will always have this extra step when deploying your html files for the first time, for example.

Upvotes: -2

Nathan Kitchen
Nathan Kitchen

Reputation: 4877

There is no hidden option to force an update of a remote repository. Only one condition determines whether the update is performed (e.g., line 239 of hg.py in the Mercurial 1.0.1 source):

if dest_repo.local():

If you're going to do some work in the working copy, you're going to log in anyway, at which point running "hg update" is pretty easy, so there's not much motivation to relax the current constraint on remote clones.

Upvotes: 5

Related Questions