Revision as of 21:32, 5 September 2018

APKBUILD mistakes

These are just my note. Please read the official guidelines.

1. Use tabs

2. Order of functions: prepare, build, check, package (the order they are executed)

3. No empty variables

4. Set Contributor and Maintainer

5. Commit message repo/package: X

X: new apk

X: upgrade to Y

X: [other changes]

6. Shell: quote variables

7. Rebase your changes

package()

1. Test APKBUILD against edge, not current

2. Make sure the software actually works

1. No downloads during build (is already prevented)

1. Don't use language-package managers (npm, pip, cabal): the build has to be

  reproducible

@@ Line 28: / Line 28: @@
 == Packages ==
-. Set pkgrel to 0 when when pkgver is increased
+* Set pkgrel to 0 when when pkgver is increased
-. Else bump pkgrel to trigger rebuild
+* Else bump pkgrel to trigger rebuild
-. Only add very common or required dependencies
+* Only add very common or required dependencies
-. Use post-install rarely, don't use it for anything that can be done during
+* Use post-install rarely, don't use it for anything that can be done during
-   package()
+package()
-. New packages go to testing first
+* New packages go to testing first
-. Use spdx license names: https://spdx.org/licenses/
+* Use spdx license names: https://spdx.org/licenses/
-. main pacakges may only depend on main packages
+* main pacakges may only depend on main packages
-   community packages may only depend on main/community package
+** community packages may only depend on main/community package
 == Testing ==