<hr /><i>wolfgang added on 2010-10-14 18:36:16:</i><br />
The new import program works like "mercurial addremove", so i think, i should rename the command.

I've started a small test repository on chiselapp.com:
  *  [http://chiselapp.com/user/wst/repository/import-vendor-test]

import/addremove and merging with cherrypick seems to work fine for me.

But i can see some problems/weak points:
  *  importing a new delivery needs to remove unused file from the source tree.
     For big projects, this might only be done by deleting the complete tree
  *  if the development branch is messed up with temporary files, which are
     not under version control, it's difficult to remove them

This could only be done, using a import directory outside of the checkout.

Merging is OK for me.

Conclusion:
  *  I'll rename import to addremove
  *  I'll analyse the code, how to do a add/remove from outside a repository.
     But this will be difficult, because i cannot use existing code. But i
     think, it will be easier to add an option --keep to update(like for open).
     So we could<br>
     1. create a new directory for the delivery<br>
     2. go to this directory and open a fossil connection with --keep<br>
     3. update this <i>checkout</i> to VENDOR without affecting the file using
        --keep<br>
     4. commit and tag the new checkin with VENDOR_n+1