On Wed, Mar 25, 2009 at 11:59 PM, Edward K. Ream <[email protected]> wrote:
> want the public files. To make this scheme work, we would want a way > to force users to commit public/private pairs of files in synch. This > is possible in principle, but I'm not sure how easy it would be. In > the worst case, Leo users could fall back on @auto, but we really > would rather avoid that sad eventuality. Hashing to rescue! For file foo.py ver 3, we have a private version 2368237aaee.txt.py. The name is the hash digest of contents of foo.py. So, when you open foo.py, leo will look up the right private filei in a priv file repo. People can commit their private files a bit off-sync, as long as the right files end up in the repo at some point. > BTW, it might be good for this case to put all files containing > sentinels in a single place, so as not to overly pollute the directory > structure in the repository. Yeah, that's the repo :-). Like we have .bzr, we can have .leo_structure in project root. If you send out a leo tree somewhere (release), you will also ship that dir. GC can be done every now and then. > Unless I am horribly mistaken, @file! promises to relegate the > (absolutely essential) sentinels to the background for almost all use > cases. In effect, we get all the advantages of @thin nodes in all use > cases. Why not keep calling it @shadow, becase that's what it still remains? The difference is that shadow files are also public files now. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
