I recently did a rant on twitter[0] on how release/download pages of various languages/tools get it wrong, especially with respect to giving EoL Dates/policy and a list of supported releases. This is my attempt at solving the problem. If you have to every check the EoL date of anything, or if you have to verify that the version you have is supported, just visit endoflife.date/toolname. The website runs on Netlify, an…
I like it! It would be nice to have (you knew this was coming, yes?) an API, whereby one could programmatically request, say, https://endoflife.date/api/os/ubuntu/16.04 (Haven't thought through the semantics.) Digression alert. I've been thinking of a multi-OS package analysis database that I wish existed. The idea being, a database of information on packages to answer questions like: - Which packages of what OSes in…
- packages don't have the same name across distributions: python or python2? python or python3?
- most binaries don't have the same checksum (except scripts that aren't compiled: not many files)
- paths tend to change across distriutions: usual Linux has /bin/bash, FreeBSD has /usr/local/bin/bash, NixOS has... something else.
The closest I can think of are the per-distro databases, along with security advisories:
- warning: huge page hxxps://packages.debian.org/stable/allpackages ; https://www.debian.org/security/dsa-long
- https://www.archlinux.org/feeds/packages/ https://security.archlinux.org/
- http://pkg.freebsd.org/FreeBSD:12:amd64/latest/ https://www.freebsd.org/security/advisories.html + http://vuxml.freebsd.org/
- etc.