On Feb 21, 2017, at 7:07 PM, Petr Ferdus <[email protected]> wrote: > > Would anyone suggest possible workaround for Unix with no way to open > repository placed in root of filesystem?
Who says you have to use just one repository for all of the directories you manage on the whole system? Why not have one Fossil repo for each subtree? That not only gets around the problem you’re having, it probably makes more sense anyway. For example, I have ~/.vim under Fossil’s management, but it’s opened as /home/mylogin/.vim on the Linux boxes, and /Users/mylogin/.vim on my macOS box. If I’d checked that directory into a repo whose root is the same as the filesystem root, I’d have a Linux-specific or macOS-specific repo. This doesn’t solve the problem for your read-only directories, but I’m a bit puzzled why you’d want those to be managed by Fossil anyway. The core premise of Fossil is that you’re tracking the change history of files, which implies that you can *change* them. If some other user can modify those files, *that* user should own the Fossil repository for those files. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
