Hi Vincent
Yes It is possible to fix and I worked on that on or off in the last two
years. It's not a high priority as Repology is also rewriting their
stuff in Rust and has not yet updated their requirements list.
In the basics it boils down to somebody maintaining this file here
https://github.com/repology/repology-updater/blob/master/repology/parsers/parsers/openindiana.py
that grabs the catalog json from our package server and parses it. There
was a move to simplify parsers but since they have moved to playing
around with this code here
https://github.com/repology/repology-rs/tree/master/repology-updater/src/parsing/parsers
we might be more served by simply porting some of my work from here
https://github.com/Toasterson/forge/tree/develop/crates/repology to
generate suitable metadata for them to their parser. And maybe add some
more metadata action to our packages.
With my current speed and schedule I seem to get to the depot server
parts here https://github.com/OpenFlowLabs/ips/ in about a month or so,
having worked more on the catalog/client code at the moment.
If you wish to help with coding or with just mailing around to the
Repology people where we could find an current guide for requirements
that they want from our metadata that would be awesome.
-Till
On 8/28/25 07:21, Vincent Torri wrote:
Hello
when using repology, OpenIndiana is not listed (see for example
https://github.com/davea42/libdwarf-code at the bottom)
While OI is listed in https://repology.org/repositories/statistics,
there is a notice concerning the repository. See
https://repology.org/repository/openindiana . It is also said that OI
repository in repology could be removed
Do you think that it is possible to fix this ?
Vincent Torri
_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
