I mostly follow -stable, and have scripts/tools that enable me to (re)build
stable from source with minimal human intervention.

To further automate this process, it would be helpful to have the current
release number and (at least) the most current patch number.

Obviously this information is clearly documented in various web pages, and if
absolutely necessary,
I could extend my toolset to scrape this info from the website and/or the www
directory in CVS,
but I am wondering if this information is already available somewhere as
data?

I've found that www/build/Makefile contains:

        STABLE_VERSION= 5.8

So that is one place I could look, although I am not excited about having to
parse a Makefile either, but I haven’t yet
found anyplace where the patch numbers are available as non-html data.

One approach would be to scrape http://www.openbsd.org/errata.html
<http://www.openbsd.org/errata.html>, and figure out the release numbers, and
then scrape the errata page of a particular release to obtain the patch
numbers.

Is this information available somewhere in the tree in some easily parseable
format (YAML, JSON, etc) ?

If not, I’ll proceed to scrape this info.

It seems to me that the errata.html and errata<release>.html files could be
generated from the kind of data source
I’m describing, and that both the resulting html files AND the data source
file could then be statically served from the website.
If this isn’t the way these files are generated today, and if there were
interest in migrating to this approach, I would
be willing to develop and contribute the code to implement that…

Reply via email to