how to workaround rpm dependency?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 196
- Forks
- 55
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 14
Description
Hi bootupd team,
I love the idea behind bootc so I've been trying to create a bootc image based on archlinux.
As part of creating a bootc image bootupd backend generate-metadata is called but this fails on arch linux as there is not rpm binary.
Is there a way I can work around this dependency? I am happy to hack around this in my image as it is just a proof of concept but not sure what to do
Also the readme suggest bootupd should be OS agnostic but looking for rpm means it is not really agnostic :-( are there plans to remove this dependency?
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 with the bootupd backend generate-metadata entry point and trace where the rpm binary is required when running on Arch Linux. Determine whether the issue needs a documented workaround or removal of that dependency; done should include a working Arch Linux path and coverage for the relevant metadata-generation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux, rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100