On 14 January 2011 02:44, Richard Hipp <[email protected]> wrote: > > On the homepage http://www.fossil-scm.org/ on the right-hand column is an > link for "Doc Index" which takes you to > http://www.fossil-scm.org/fossil/doc/trunk/www/permutedindex.wiki which is > a good place to go to look for information about Fossil. >
That helps a lot :) Now, as I understand it searching for content on the wiki pages is not going to be easy / supported, as the wiki pages are in fact stored as compressed artifacts. My guess is that the choice of doing this is based on simplicity and reuse or the versioning infrastructure. However this is at the cost of search :) If I've got that clear - then there would seem to be only a couple of ways to add searchable metadata to the documentation: 1. Create a seperate non-versioned but searchable db before submitting the wiki page to Fossil, and link this to the sha1 2. Do something clever with Fossil tags, and then use fossil sql to execute a search In terms of feature requests, I would have thought that an option to create a searchable index of the wiki content for only the latest commit would be possible? This is what is already done for other metadata: The current implementation of Fossil stores each artifact as a BLOB in an > SQLite database. The current implementation also parses up each control > artifact as it arrives and stores the information discovered from that parse > in various other SQLite tables to facilitate rapid generation of reports > such as timelines, file histories, file lists, branch lists, and so forth. > Would appreciate your thoughts on future directions here / corrections.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
