Talk:Creating an Alpine package

From Alpine Linux
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Under "commit your work", there's a thing to

cd $aportsdir
git pull

This should pull all the changes made by others into you local git repo. When you think you are ready you can add your files to git:

cd $apkbuilddir
git add APKBUILD (include any other files needed for the build; $pkgname.install...)
git commit


What is the difference between $aportsdir and $apkbuilddir?

Is apkbuilddir $aportsdir/$pkgname ? Or can $apkbuilddir be ~/work/foo/packagename


--Nangel 20:05, 12 August 2010 (UTC)

Install section

The wiki mention:

APKBUILD should have the install variable defined and the scripts should also be added to the source variable

but when doing this abuild warn:

>>> WARNING: <aport>: You should not have $install in source

so I guess this should be remove, correct me if I'm wrong

— Preceding unsigned comment added by Steeve (talkcontribs) 12:53, 6 April 2015

Test your package

what i was missing after building, was how to test

#after abuild -r
apk add /home/$USER/packages/main/$ARCH/$PACKAGE_NAME.apk

--Hauke Löffler (talk) 22:21, 1 February 2017 (UTC)


Dead link

During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!

The web page has been saved by the Internet Archive. Please consider linking to an appropriate archived version: [1]. --Gopherbot (talk) 08:24, 4 September 2023 (UTC)