Pristine text handling - musing on what angle to take next week

I've been studying the pristine text handling, and made a bit of
progress in the update editor. There are several angles from which I
could continue:

    - Installing the new pristine during commit. (Update and commit are
the two places that need to install one, except for "copy" which
installs a copied text base in WORKING_NODE.)

    - Retrieving the pristine from the new store instead of from the old
one. For transition (while "update" puts a copy in the new store but
"commit" doesn't), I could make it look in the new store first, then go
to the old one if not found.

    - MD5 vs. SHA1 - adapting code that gives/takes MD5 sums so that it
gives/takes SHA1 sums as well or instead.

I'll think on these and look at some or all of them, but any thoughts in
the meantime?

(Greg's been telling me about plans for update to end up with calling
__global_update() which will do pretty much the whole DB and local files
steps necessary to update to a new base version. Sounds good. At the
moment we're using little DB manipulations here and there along the WC-1
code path.)

- Julian
Received on 2010-04-09 17:48:46 CEST