indygreg / indygreg/PyOxidizer
Consider using existing library "rpmrepo_metadata" for reading RPM repository metadata
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/dralley/rpmrepo_metadata/
Disclosure: I wrote this library
To my knowledge it is the most complete implementation that currently exists in Rust by a large margin and I'd welcome further contributions. Updateinfo support is not 100% complete yet, nor is writing repository metadata, nor the documentation, but parsing the standard metadata is essentially done and decently tested.
I haven't put out a release on crates.io yet, because I have mostly been using it for a personal project and didn't realize there was much demand (and also I became a maintainer of quick-xml and got sidetracked fixing bugs in that library that I ran into...), but I can fix that shortly.
Also note that despite the example in README.md using the Python bindings, the Rust API is complete.
edit: Now fixed. https://crates.io/crates/rpmrepo_metadata
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked rpmrepo_metadata library and locating PyOxidizer's existing RPM repository metadata handling. Determine which metadata parsing or integration work is still needed, then verify the result against the project's packaging tests; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100