User:Ganwell/mistakes: Difference between revisions
No edit summary |
|||
Line 5: | Line 5: | ||
== Style == | == Style == | ||
* Use tabs | |||
* Order of functions: prepare, build, check, package (the order they are executed) | |||
executed) | |||
* No empty variables | |||
* Set Contributor and Maintainer | |||
* Commit message repo/package: X | |||
** X: new apk | |||
** X: upgrade to Y | |||
** X: [other changes] | |||
* Shell: quote variables | |||
* Rebase your changes | |||
== Packages == | == Packages == | ||
Line 47: | Line 46: | ||
== Testing == | == Testing == | ||
* Test APKBUILD against edge, not current | |||
* Make sure the software actually works | |||
== Build == | == Build == | ||
* No downloads during build (is already prevented) | |||
== Languages == | == Languages == | ||
* Don't use language-package managers (npm, pip, cabal): the build has to be | |||
reproducible | reproducible |
Revision as of 21:33, 5 September 2018
APKBUILD mistakes
These are just my note. Please read the official guidelines.
Style
- Use tabs
- Order of functions: prepare, build, check, package (the order they are executed)
- No empty variables
- Set Contributor and Maintainer
- Commit message repo/package: X
- X: new apk
- X: upgrade to Y
- X: [other changes]
- Shell: quote variables
- Rebase your changes
Packages
- Set pkgrel to 0 when when pkgver is increased
- Else bump pkgrel to trigger rebuild
- Only add very common or required dependencies
- Use post-install rarely, don't use it for anything that can be done during
package()
- New packages go to testing first
- Use spdx license names: https://spdx.org/licenses/
- main pacakges may only depend on main packages
- community packages may only depend on main/community package
Testing
- Test APKBUILD against edge, not current
- Make sure the software actually works
Build
- No downloads during build (is already prevented)
Languages
- Don't use language-package managers (npm, pip, cabal): the build has to be
reproducible