It used to just ignore the beta information, but that wasn't quite right.
This does means that the library details will still have information about
the beta version after a release, which isn't desirable, but it
shouldn't be too hard to write something to strip out old beta
information.
PHP 5.4 uses UTF-8 by default, but PHP 5.3 uses ISO-8859-1 so character
encoding is going wrong there. So replace htmlentities with a function
that uses the correct encoding.
Does this fit in reduce_versions? It seems to. Maybe should make the
data structure a bit better, boost-version shouldn't change with new
releases so it could be part of some release independent data.
First remove some old code which guessed the module from the library's
key, this was there to bootstrap modules - no need now they're all
stored either in the documentation list, or implicitly by the location
of libraries.json.
Secondly, pass the name of the module as the parameter, rather than the
array containing the module data.
Which is accurate, and removes the need for a special case. If boost
build needs special behaviour, that could be set by adding an extra
entry to `$params`.
The 'display_template' mechanism is pretty rubbish. There's only ever
one template, and it's probably not flexible enough to ever be of use.
Might be best to just remove it.
Should probably actually do this in create-module-metadata, as once the
metadata is in place this script should ignore the maintainers file. But
I didn't have much time tonight. So I won't check the changes into
libraries.xml. Also need to consider that 'maintainers' should probably
be backdated to apply to all versions. Maybe it shouldn't be store in
libraries.xml at all.
It makes it easier to detect when a library's details have changes. I
could normalize when comparing, but this seems easier. It's okay to
lose this information.
