It was not long ago that I announced the deprecation of the security notificaiton report. This report depended upon manually designating a particular commit as security-related within the FreshPorts database. A lack of resources to perform this task meant that the report was rarely sent out. I suggested that everyone install and use portaudit, which uses the vuxml database, instead.
Immediately after this announcement, Chimera had the excellant idea of redesigning the security-notice report to use the vuxml data. Of course! FreshPorts already parses the vuxml data and marks each affected port ..
On Friday, while travelling the Trans Canada highway, somewhere between St-Leonard, NB, and Degelis, QC, I coded the solution[1]. Amazingly, it involved changing one table name in an SQL query. Instead of security_notice, the query now uses the commit_log_ports_vuxml table.
The code should go into production later this week.
[1] I wasn’t driving. I was a passenger. I’ve recently found that coding in a moving vehicle, be it plane, train, or in this case, automobile, can be both productive and a cure for boredom.
