I have managed <hg:pull> in my recipe though what I did is far from
intuitive... I hope it's my fault.
1) documentation says that "attribute dir = Local subdirectory with
repository (optional, defaults to '.')"
But then the value specified in this attribute is used as standalone
parameter to 'hg pull' what should be path where pull is done from.
As example: <hg:pull dir='foo'/> runs "hg pull -u foo"
... but mostly you want to pull from "default" (or no parameter for
pull source at all) (mind that "default" is a magic Hg URL puling from
where the original 'hg clone' was done from.
2) doc says that you need to specify --build-dir to bitten-slave as it
depends on existing hg repository. This is true, but it then should
say that you need --keep-files as well to prevent bitten from erasing
your Hg clone
At the end <hg:pull dir="default"/> and 'bitten-slave --build-dir=my-
hg-clone --keep-files' doeas the trick. I needed to do few experiment
to achieve this and if this is right approach the doc is definitely
misleading about @dir attribute of hg:pull.
HTH
Pavel
Not in very latest trunk and 0.6 branches. I just fixed an open ticket
for this the other day, and could you please grab the latest version
from repository and verify the fix? See:
http://bitten.edgewall.org/ticket/530
:::simon
https://www.coderesort.com
http://www.ohloh.net/accounts/osimons
this seems to work. Now I only provide --build-dir to bitten-slave
pointing to my repo clone and I do not have to cheat @dir attribute.
Many thanks
Pavel