On Thu, 26 May 2011 12:03:19 +0200, Joan Picanyol i Puig wrote: > The problem is that fossil does not support neither "good-enough" > ownership/permission tracking nor the flexibility to work around it > before/after commit. > > I hope that fossil grows either (or both :) of these features some > time, > even though they are likely not one-liners.
What about creating your own wrappers on top of fossil ? If fossil doesn't store ownership, permissions, or the temperature of the room at the time you checked in, you're still free to handle these yourself using versioned files and helper scripts ;) For example : 1. a "backup" script, which generates a file at the root of your tree, containing all the information you need (ownership and permissions for each file in the tree, symlinks ignored by fossil, whatever... a kind of "user-level manifest") and then calls "fossil commit" (and WOW, you get metadata history as a bonus !) 2. a "restore" script, which pulls/updates/checkouts/whatever, reads your "manifest" then applies the ownership and permissions on your files, creates symlinks, etc... Proof of concept (handles ownership and permissions) : - backup : http://dpaste.com/hold/546796/ - restore : http://dpaste.com/hold/546797/ These scripts should be called from the root of your checkout, or with the path to the checkout root as first argument. IMO, this is definitely NOT the goal of fossil to provide backup features out of the box... Regards, Simon _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
