Distro Packaging
- Dominant language
- Haskell
- Stars
- 744
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Hello, the readme mentions a call for packaging. What some people do is make use of CI such as travis to do this. One such project is nnn and you can check out the .travis [here](https://github.com/jarun/nnn/blob/master/.travis.yml). It makes use of [Packagecore](https://github.com/BytePackager/packagecore) which is pretty flexible.
However when it comes to the AUR you typically want to either provide a pkgbuild file or submit to the aur yourself. It's actually fairly simple, consider it a bash file with defined process.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue suggests setting up CI for distro packaging, referencing nnn's .travis.yml and Packagecore. For AUR, a PKGBUILD file is needed. Start by examining the project's existing build system (likely Cabal or Stack) and directory structure. Look at the linked nnn Travis config to understand the automation pattern. 'Done' means having a working CI script that produces packages for target distributions and a PKGBUILD for AUR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, haskell, shell
- Domain
- build-system, cli, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100