micro-editor / micro-editor/micro
Including an RPM in GitHub Releases
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
I would like to suggest an official .rpm package file of micro be included in the releases section going forward.
This would make installation and maintenance easier for those using an RPM compatible distributions which does not have micro in its repositories, has an outdated version of micro in its repositories, or environments where a direct RPM download from the 'official source' is preferable and/or mandatory to use instead of one created by a 3rd party. There is already a .deb package for the distributions which support those, which is advantageous for the same reasons.
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 tracing the release process that produces the existing .deb package and how release artifacts are attached. Determine where an official .rpm artifact would fit for RPM-compatible distributions; done means a documented, repeatable RPM package is included in future GitHub Releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- 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