Talk:Creating an Alpine package: Difference between revisions
(→Install section: new section) |
|||
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>>>> 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 |
Revision as of 16:53, 6 April 2015
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