In the admin settings page it reads: "Settings marked with (v) are 'versionable' and will be overridden by the contents of files named .fossil-settings/PROPERTY. If such a file is present, the corresponding field above is not editable."
It seems that the fields are only "uneditable" if you use fossil ui or fossil server (or some way of browsing from an open checkout) but not for a CGI session. It makes sense that it works this way because it is relatively easy for fossil to look at the file system of the open checkout to detect if there is a versionable setting and modifying the generated html appropriately, but is probably far more difficult to look into the repository to see if those files exist (and if they do, do they exist for the current trunk, or tip, or whatever). Perhaps "impossible" is a better word, since the versionable settings have to exist in a given commit, and being versionable you would what whatever current commit is open to be the versions of the settings in use. Since a CGI session is using a specific repo, not an open checkout. Okay, sorry for the rambling. I was thinking of using the versionable settings as a way to avoid pulling configuration settings from the master to my remote repositories, but now this is seeming like a less than perfect option, because the CGI of the master can't see the same settings information that my open checkouts see. Am I missing something? Is it possible for the CGI to see the versionable settings, or am I correct in my reasoning as to why? -- Scott Robison
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users