Right now, the list of packages is computed at code writing time by using the go list command, and writing the result to a map in packages.go file.
This has three problems:
it's missing some valid packages (with issues filed) that are hidden via build constraints
it's missing some previously-valid packages (with issues filed) that got moved/removed at latest version
it requires manual re-generation, which happens rarely, and the list is therefore often stale
It would be better to have this list of packages (directories, really) to be maintained dynamically.
This can be implemented by watching the relevant git repositories with source code for new commits to the master branch, and the release branches for the supported versions of Go (i.e., current and previous releases), and walking the tree to find all directories that exist.
Right now, the list of packages is computed at code writing time by using the
go listcommand, and writing the result to a map in packages.go file.This has three problems:
It would be better to have this list of packages (directories, really) to be maintained dynamically.
This can be implemented by watching the relevant git repositories with source code for new commits to the master branch, and the release branches for the supported versions of Go (i.e., current and previous releases), and walking the tree to find all directories that exist.