Rpm repository improvements
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm not sure if this is the correct place to report, but this is a few improvement proposals for the linux rpm repository and the keybase.repo file.
- As it works now, the keybase rpm installs a keybase.repo file to /etc/yum.repos.d/. This is quite OK, but the more traditional way is to also provide this repo file in the online repository. This is so that people could automate their software setup by issuing:
sudo dnf -y config-manager --add-repo=https://prerelease.keybase.io/rpm/keybase.repo
sudo dnf install keybase
- There is no source rpm available in the repo. I know the source is available, but it is more like a thing of being able to show that the rpm can be rebuilt from the source rpm, thus being able to prove the chain of trust and integrity.
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
Review the RPM packaging and repository configuration that produces keybase.repo and publishes the online repository. Verify that the documented dnf config-manager URL works, then determine how source RPM artifacts could be published and rebuilt to satisfy the requested chain-of-trust check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100