www/64120: /mnt/www/en/ports/needs to be re-run

[Mark Linimon]

> The idea I have been thinking about was e.g. using the INDEX file
> already generated elsewhere (e.g. the INDEX tinderbox kris already runs)
> for the build on www.  But it was just an idea, and I have no plans to
> work on that at the moment.  Also I haven't looked more closely into the
> consequences of doing this (with regards to mirrors).

As a suggestion, the Ports Monitoring database already has its own
internal representation of much of the metadata, with the exception
of the dependencies.  It has the advantage of being no more than one
hour out of date -- it knows to incrementally update individual ports'
metadata based on the output of a ports cvsup.  Pieces of it could
be recycled to do this kind of function, or it could create a report
that could be grabbed.

No doubt, this could also be done based off of FreshPorts' database,
which probably has a nearly identical set of metadata.

mcl