Talk:Creating an Alpine package: Difference between revisions

From Alpine Linux
(→‎Install section: new section)
(→‎Test your package: new section)
(One intermediate revision by one other user not shown)
Line 27: Line 27:
but when doing this <code>abuild</code> warn:
but when doing this <code>abuild</code> warn:


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


so I guess this should be remove, correct me if I'm wrong
so I guess this should be remove, correct me if I'm wrong
== Test your package ==
what i was missing after building, was how to test
<pre>
#after abuild -r
apk add /home/$USER/packages/main/$ARCH/$PACKAGE_NAME.apk
</pre>
--[[User:Hauke Löffler|Hauke Löffler]] ([[User talk:Hauke Löffler|talk]]) 22:21, 1 February 2017 (UTC)

Revision as of 22:21, 1 February 2017

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

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)