I have a few scripts to maintain my repositories, and among other things, they add (and update) multiple flavors of (unversioned) wiki homepages (the remote homepages have more links, such as login/logout/index, and the local ones show a reminder about syncing).
Some repositories have customized wiki homepages, and for these I would like to skip the updates of the default homepages. It seems like a simple solution to add a custom value to Fossil's `config' table to indicate whether or not the homepages are customized. Is this a safe and encouraged approach? Is it harmless but discouraged, or even harmful? Would such custom values be excluded from syncing? This task seems more complicated to do with the `fossil uv' interface, as it doesn't allow to query the hashes or time stamps of unversioned files. Also, not sure if wiki pages allow embedded comments (standard HTML comments do not seem to work?) that could be searched for custom settings? Another approach I see is keeping custom configuration data in unversioned files of their own. Or does anybody know of a better method? --Florian _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
