On Wed, Feb 9, 2011 at 12:32 AM, Andreas Kupries <andre...@activestate.com>wrote:
> So, such a bundle really is in essence a .zip with a bit of additional > information. > Thanks for that clarification. Another idea came to mind after i signed off last night... creating the bundle as a second sqlite db (not a fossil db), which fossil internally ATTACHes for purposes of populating it or importing it. That would should allow us to use fossil's existing logic (with minor tweaks?) for matching up the patch revisions against the main repo. The patch db would contain whatever info a manifest normally does, plus the deltas (or new content) and the revisions (from the main repo) to apply them to. Patches matching unknown main repo revisions should (probably) be rejected. i like the sound of that, but i still wouldn't have a clue where to start implementing it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
