vendor branch import

[Zoran Bosnjak]

>> But what if a vendor code IS the project itself.
> If you are importing snapshots of vendor_lib why does it matter where it
> is placed in the project that uses it?

If a vendor code is placed in toplevel of a project (not in a
subdirectory),
then I can not run "$rm -rf libexample" as written in your example.
I need to run "$rm -rf *" and then check what .files are also to be
removed.
This is manual work which I would like to avoid with proper procedure.
What I need is a method to delete ALL files from '.', but mercurial files.

I fully understand the concept you described. But could you please rewrite
your example and place libexample on a toplevel of a project, like this:

  mkdir work
  cd work
  tar -xvzf /var/tmp/examplelib-1.0.tgz
  mv examplelib-1.0 examplelib
  cd examplelib
  hg init .
  hg addremove
  hg commit -m "v1.0"

... then you receive examplelib-2.0.tgz
How do you import it to repository in this case?
Remember: 'work/examplelib' is project root, not 'work'.

Zoran