More than a year ago I talked with espie@ about making the sqlports info
available as a json file in the CDNs/mirrors. My idea was to provide
that info for people who want to create simple/static javascript web
pages, external tools for monitoring the ports tree or some type of
automation system.
Nobody wants to maintain a dynamic web page to show info about the
ports. We had one (i can't even remember the domain) and was
decommissioned long time ago. A static web page reading the json from
the CDN with javascript would be quite easy to maintain. Also, other
webs could use the info (like repology.org). Or tools like [1]. You
could compare packages between versions of OpenBSD without uncompress
various copies of sqlports.
Everything would be generated by a simple python port during the bulk.
The script is now 20 lines and takes less than 10 seconds. The files
would be copied to pub/OpenBSD/{snapshots,version}/packages/arch. Maybe
only to amd64, because the info is the same. I abandoned the idea one
year ago because I wanted to convert the table Ports and the json was
27MB[2]. Now I'm splitting a limited part of Ports in small json files.
Examples:
1,3MB, FullPkgPath, COMMENT, MAINTAINER
https://juanfra.keybase.pub/tmp-ports/packages-info.json
1,1MB, FullPkgPath, DISTNAME, FULLPKGNAME, PKGNAME
https://juanfra.keybase.pub/tmp-ports/packages-versions.json
1,7MB, FullPkgPath, BUILD_DEPENDS, LIB_DEPENDS, RUN_DEPENDS, TEST_DEPENDS
https://juanfra.keybase.pub/tmp-ports/packages-depends.json
I've the python script but I've not started yet with the port. The
question for the porters (and in special people running the bulks,
signing/uploading packages) is, are you against this idea?.
1. https://github.com/danieljakots/obsd-ports-tools/blob/master/showvictims.py
2. https://juanfra.keybase.pub/tmp-ports/sqlports-everything.json
--
Juan Francisco Cantero Hurtado http://juanfra.info
