Please improve packaging documentation (context, testing)
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 3.3k
- Forks
- 446
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 1
Description
The Creating Packages page is missing a few poins which would be worth documenting:
- starting context: for those who have not packaged anything yet (e.g. how to obtain makepkg and makepkg-mingw, does it run under Windows, under Linux, or is it Arch-only?).
- testing the package: can I test the packaging under Linux? Is there a docker image ready for that?
I am running the crossroad cross-build environment and would like to test a new PKGBUILD (before creating the PR for it) locally, running Ubuntu (or Docker or anything else).
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 Creating Packages page linked in the issue and verify the package-building prerequisites and supported environments. Check how makepkg and makepkg-mingw are obtained, whether crossroad supports local testing on Linux or Docker, and document the confirmed setup and testing path for someone preparing a PKGBUILD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100