Talk:Newbie Guide to Building an apk: Difference between revisions
(explain how ./new works) |
m (Unsigned comment attribution. RfD.) |
||
| Line 1: | Line 1: | ||
{{Delete|The [[Newbie Guide to Building an apk|Page]] associated with this talk page does not exist}} | |||
The ''make new APORTS="somepackage"'' have been replaced with a new script: | The ''make new APORTS="somepackage"'' have been replaced with a new script: | ||
./new ''somepackage'' | ./new ''somepackage'' | ||
| Line 25: | Line 27: | ||
If the apk package works then you can use ''svn diff fmtools > fmtools-aports.patch'' to create a patch to send to the mailing list. | If the apk package works then you can use ''svn diff fmtools > fmtools-aports.patch'' to create a patch to send to the mailing list. | ||
<small><span class="autosigned">— Preceding [[Help:Signature|unsigned]] comment added by [[User:Ncopa|Ncopa]] ([[User talk:Ncopa|{{int:talkpagelinktext}}]] • [[Special:Contributions/Ncopa|{{int:contribslink}}]]) 10:47, 25 December 2007</span></small> | |||
Latest revision as of 04:14, 14 August 2023
 The Page associated with this talk page does not exist
(Discuss) |
The make new APORTS="somepackage" have been replaced with a new script:
./new somepackage
So with the fmtools example it would be:
./new fmtools
This will create the Makefile for you.
At this stage you might want to add the new Makefile to svn in case you want to commit the aport (or send a patch)
svn add fmtools
the output will be:
A fmtools A fmtools/Makefile
then to create the apk:
cd fmtools/ make
Output will be:
depscan: scanning aports: libc.so.0 depscan: found: libc.so.0 (uclibc) Unpacking fmtools-0.99.1.tbz2 for fmtools Building fmtools-0.99.1.apk
If the apk package works then you can use svn diff fmtools > fmtools-aports.patch to create a patch to send to the mailing list.
— Preceding unsigned comment added by Ncopa (talk • contribs) 10:47, 25 December 2007