parseable representation of portage tree

[_Razorblade_]

I'm looking for a parseable representation of the portage tree, ideally as json. The goal is to parse it using renovate custom datasource to find version changes when running renovate as bot.

If there is no export yet, which (portage or 3rd party) tool could be used to easily generate such a representation?

I looked at soko (which generates packages.gentoo.org) and it seems to be doing a great job of parsing ebuilds and updating a backend database - it just has no usable output for me.

[Genone]

Well, if I understand you correctly you just need an adapter to make the soko database available via HTTPS so it can be accessed by renovate (disclaimer: I'm not familiar with any of those tools).
Soko seems to use a PostgreSQL database, so there is a chance that something like that already exists in some form. And postgreSQL itself seems to have some support to format query results as JSON output. So shouldn't be too difficult to build such an adapter yourself if you have some basic knowledge of SQL.

[_Razorblade_]

I'm looking for a source that can be queried as part of a CI pipeline, i.e. a daily check if the available version of a specific application has changed. Setting up an (always running) Postgres server for this purpose seems to be a bit of an overkill. Maybe looking at soko was misleading - I was just asking myelf what is being used to serve packages.gentoo.org, because that basically contains the information I need. Maybe I'll look into parsing the html response if no other idea comes up.

[logrusx]

I think eix can check for available updates but I'm missing the syntax for that. I glanced at its man page and found --upgrade or -u which sounds like that. Further more you can alter its default output to something more convenient for further processing.

Best Regards,
Georgi

[Ralphred]

[logrusx]