[Monotone-devel] Scenario for tracking upstream package

[jplejacq]

I'm wondering what the "monotone way" is for the following scenario.

I would like to track changes to a third party package that uses CVS
for source control.  I'll be making my own changes but want to stay
consistent with the upstream package.  With cvs, I would normally
use a vendor branch for this.

This is what I've tried:

1) I download the third party package and add all files to a newly
   created monotone database using a branch called "vendor".

2) I then copy the package directory structure to another
   directory and add this to the same monotone database using
   another branch called "local".

3) I then edit files on the local branch and commit them to the same
   branch.

4) When an upstream release is made, I download it to the original
   directory and commit any changes to monotone on the vendor
   branch.  This probably isn't sufficient since file deletions and
   renaming aren't accounted for.

5) I then use the monotone's propogate command to merge changes in
   the vendor branch to the local branch.

Is this reasonable?  It would be nice to have a cookbook of some
common scenarios like this.

-- 
JP