baz-import explosion

[Jamie Wilkinson]

This one time, at band camp, Aaron Bentley wrote:
>Jamie Wilkinson wrote:
>| Hi!
>|
>| After having fiddled with bzr on and off, I decided to import some
>code from
>| baz; I got bzrtools-0.6.1 and unpacked it into ~/.bazaar/plugins; i'm
>| running bzr.dev last updated sometime last week (bzr log tells me it's
>revno
>| 1384).
>|
>| I assume I can run it from a checkout of a baz branch, and tell it the
>name
>| of a bzr branch to import into (based on the Notbrancherror I got when I
>| didn't bzr init the target -- I was kinda hoping it'd create the
>directory I
>| specified and init it for me :)
>
>It does.  That's actually what the problem is.  On the first run, you
>must specify the name of a directory that does not exist:
>
>bzr baz-import $NEW_DIR foo at bar--lala/category--branch--version

No, the problem was that I had no tla branch name in the command.  It turns
out baz-import will work just fine with an existing directory that's been
bzr init'd.

You're probably right about it assuming it's from a previous import though,
but I think in this case it's working because bzr init is the null import.
(wild guess)

So, what's the actual recommended way of running bzr-import?  Do you have to
run it from a checkout of the branch, and give the branch name?

>
>| Oh, I also am using a brand spanking new checkout of pybaz, and
>modified the
>| top of bzr_import.py in bzrtools to make sure it's in the library path.
>
>All you have to do is stick a symlink to pybaz in your bzrtools
>directory.  I ensure the bzrtools directory is in your path in __init__.py.

Oh, neat.  Thanks.