On Thu, Aug 28, 2025 at 7:31 PM Till Wegmüller <toaster...@gmail.com> wrote: > > 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.
So you have ported ips from python to rust ? that IS nice :) > 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. unfortunately, i'm not a python guy, nor a rust one (i prefer C, or zig). I can ask Repology devs best regards Vincent Torri _______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
