I had the idea of adding a single optional JSON object as meta-data to each unversioned file. Having such metadata, and publishing it as part of the /juvlist output, would facilitate new features in pages such as the Fossil Download page that are drawn based on which unversion files are available. (See https://www.fossil-scm.org/fossil/doc/trunk/www/aboutdownload.wiki for a description of how the Download page currently works.)
The meta-data on each unversioned file could identify the target platform (linux, max, openbsd, windows, source-code), and the release version, and perhaps other meta-data. Such information is current transmitted using file-naming conventions. Breaking it out into explicit meta-data seems to be a better design choice. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
