Include:Newapkbuild: Difference between revisions
Prabuanand (talk | contribs) (revert back the redirect as it causes the issues in Creating an Alpine package page) Tag: Removed redirect |
Prabuanand (talk | contribs) (used the content from Creating an Alpine package page) |
||
Line 1: | Line 1: | ||
The <code>newapkbuild</code> tool, which is installed as part of the {{Pkg|abuild}} package, can create a new APKBUILD template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details. {{Cmd|newapkbuild ''packagename''}} | |||
'''newapkbuild options''' | '''newapkbuild options''' |
Revision as of 07:12, 18 February 2025
The newapkbuild
tool, which is installed as part of the abuild package, can create a new APKBUILD template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the package policies page about naming details.
newapkbuild packagename
newapkbuild options
- -n Set package name to NAME
- -d Set package description (pkgdesc) to DESC
- -l Set package license to LICENSE
- -u Set package URL
- -a Create autotools package (use ./configure ...)
- -C Create CMake package (Assume cmake/ is there)
- -m Create meson package (Assume meson.build is there)
- -p Create perl package (Assume Makefile.PL is there)
- -y Create python package (Assume setup.py is there)
- -s Use sourceforge source URL
- -c Copy a sample init.d, conf.d, and install script to new directory
- -f Force even if directory already exist
- -h Show this help
The manual page (available via man newapkbuild
) describes all options for newapkbuild
.