I want to share my thought about symlinking in fossil. I like that fossil manages files only and not other things like directories*, permissions, symlinks and maybe ACLs. There is "empty-dirs" setting and I'm okay with it, since it can be stored as file. And I think all these things are OS specific and should be managed identically. I mean, I expect them to be managed in different setting groups. Or maybe create one group, since there would be too many settings. Where content could be something like this:
dir "my_empy_dir" dir "my_empy_dir2" ln "existing_file_in_repo" "new_link" ln_hard "existing_directory_in_repo" "new_hard_link" attr_executable "bin/*.sh" attr_hidden "*.cab" That setting can be applied whenever "empty-dirs" is currently applied. What should "ln" do on FAT16/32 and exFAT filesystems? Well, I'd just expect fossil to not bother creating any links and maybe give a warning. On Windows XP+ I'd expect native NTFS links. That's all. Hope I was clear, it's 1:30AM here. On Mon, Oct 16, 2017 at 10:49 PM, Andy Goth <andrew.m.g...@gmail.com> wrote: > On 10/14/2017 5:16 PM, Andy Goth wrote: > > Please review the enhanced-symlink branch. I can't test it properly > > this weekend because I don't have Windows anywhere at home. > > Tested on Windows 7, works just the way my project needs it to work. > The manifest.symlinks file is created when the "l" flag is present in > the manifest setting. On Windows (not Unix), its contents determine > what files are and are not considered to be symlinks. Editing the file > influences the changes, status, and commit commands. > > I'd like to merge enhanced-symlink to trunk, but honestly I am afraid to > just do so even though it passes all my tests because there's been zero > mailing list discussion, aside from talking about Windows symlink > functionality present on other branches which were themselves never > merged to trunk. > > I still do not know my original change was moved off trunk. It didn't > break compatibility, and it did provide a significant part of the needed > functionality: listing symlinks in a way I can see them in Windows, > short of parsing the manifest (another question I asked about that never > got any replies on the mailing list). I asked for clarification for my > code being moved off trunk but never got any. > > Now I see my most recent trunk check-in has also been moved off trunk, > despite also not being a compatibility issue, with no explanation to > either mailing list, my private email, or the check-in comment. I'm > talking about http://fossil-scm.org/index.html/info/eb4dda482056b1db. > > Was there some policy change about committing to trunk that I missed out > on? Before I spend any more time working on Fossil I need to know that > I'm not doing something unwelcome. > > -- > Andy Goth | <andrew.m.goth/at/gmail/dot/com> > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- I remain, Arseniy Terekhin
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
