dalehenrich/filetree — Issue #2: does adopt work for repairing ancestry?
Author: dalehenrich
Created: 2012-02-02 20:09:29+00:00
State: open

The expected life cycle for packages stored in disk-based repositories (like git and svn) is:

1. aaa-dkh.1.mcz created as mcz file
2. aaa-dkh.2.mcz created as mcz file (ancestor aaa-dkh.1.mcz)
3. aaa-dkh.3.mcz created as mcz file (ancestor aaa-dkh.2.mcz)
4. aaa-dkh.3 copied to filetree repository (empty ancestry)
5. aaa-dkh.4 created in filetree repository (empty ancestry)
6. aaa-dalehenrichs.4 .mcz created as mcz file (ancestor aaa-dkh.3.mcz)

Now the situation exists where one would like to merge aaa-dalehenrichs.4 .mcz into aaa-dkh.4 in the filetree repository ...

In order for this to work i postulate that the following steps would work:
1. load aaa-dkh.4 into image
2. ADOPT aaa-dkh.3.mcz as ancestor (I think thats the sematics of adopt)
3. now merge aaa-dalehenrichs.4 .mcz and aaa-dkh.3.mcz should be the common ancestor

If these steps don't work we'll have to come up with something that will work ... otherwise we'll have to keep up-to-date ancestry information in the filetree repository which is not desirable...