What if we had something like this: <errata release="3.7"> <patch id="12" name="copy" type="security" date="2005-03-16" arch="amd64"> More stringent checking should be done in the <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=copy&sektion=9";>copy(9)</a> functions to prevent their misuse. </patch>
<!-- more patches here --> <patch ... > <patch> </errata> We would be able to build the respective errataXX.html from it, separating format from content, and providing at the same time a kind of RSS feed for those who want it (like me). The benefits would be many: For developers maintaining errataXX.html: - One single place for changing the format of _all_ the errataXX.html pages (layout, links to new releases, colors, ...) - No need to mess with HTML when adding a new patch, except for writing the patch description. - No more errors because of copying an old errataXX.html as a base for writing the new errata.html We could even use it for sending a mail automatically to security-announce@ For translators: - Focus on translating the text only - No need to track changes in the format of the pages any more :) For users: - A simple, easy to parse file for getting errata up to date - Eases the writing of scripts for automating patching XSL would do the magic here. It would be as easy as: $ xsltproc errata.xsl errata-37.xml > errata37.html We only have to edit errata.xsl to change the layout/format for all the errataXX.html files. We could even write a Makefile for that. errataXX.html would be not the only pages generated from a script (groups.html is already generated from one). If any developer/translator/user is still reading this and thinks it would be good idea ... you can find two samples and the XSL script in the URL provided below. It's a working _prototype_ that I could developer further if it is of any interest. It may lack of many things yet (update date & time comes to mind). http://www.openbsd.org.mx/santana/errata/ -- Gerardo Santana
