I use symlinks *very* heavily. Almost exactly 10% of the files in my main fossil hierarchy are actually symlinks. Fossil not supporting them would be a huge drawback for me. Good support for symlinks and nested repositories are 2 of the details I like best about Fossil (in addition to the obvious features).
../Dave On 27 November 2017 at 18:20, <bytevolc...@safe-mail.net> wrote: > On Mon, 27 Nov 2017 09:52:19 -0500 > Richard Hipp <d...@sqlite.org> wrote: > > > I am in receipt of your patch. I have not evaluated it yet because > > the entire symbolic-link mechanism in Fossil is confused and very > > difficult to manage. It mostly works now, but is brittle. A > > seemingly simple patch like what you sent could cause breakage. > > Perhaps a separate function "make_path()" just to create any > directories that may not exist, rather than stuffing it all in > blob_write_to_file(). It can be called as follows if needed: > > make_path(zFile); > blob_write_to_file(&content, zFile); > > > > > I am very sorry that I allowed symbolic link support into Fossil in > > the first place. (Symbolic link support was neither designed nor > > written by me - it is contributed code.) I would really like to get > > rid of symbolic link support. Symbolic links seem out-of-place in a > > version control system. As implemented, symbolic links are a point of > > confusion which (as far as I can see) adds no useful capabilities. > > Are you referring to symlinks inside a working directory, or Fossil's > ability to "follow" them? If so have a survey of users, or a > disabled-by-default policy to see if any users need it. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
