Aports tree: Difference between revisions

From Alpine Linux
m (spelling)
Line 17: Line 17:


== Create a APKBUILD ==
== Create a APKBUILD ==
Your are encouraged to contribute with APKBUILD's the you have made.<BR>
You are encouraged to contribute the APKBUILD's that you have made.<BR>
Please look at [[Creating_an_Alpine_package|Creating an Alpine package]] page that describes how you make your own APKBUILD's.
Please look at [[Creating_an_Alpine_package|Creating an Alpine package]] page that describes how you make your own APKBUILD's.

Revision as of 21:51, 7 September 2011

Introduction

The aports tree is a directory tree with many APKBUILD's. APKBUILD is a file containing "recipes" on how something should be built/compiled. These files are used when building alpine from source. In your build environment you would have at least one APKBUILD for each package/program.

When alpine is compiled, you will no longer see (or have use of) the APKBUILD. It is not included in the 'iso' or 'tar.gz'.

The abuild script reads the APKBUILD and executes the steps needed to create a package.

Fetch latest APKBUILD's

While inside your build environment you need to install some needed packages and you need to fetch the APKBUILD's from the server (fetch the aports tree).
Note: You only need to do these 2 steps once! Next time you can skip this part.

apk add alpine-sdk

cd ~

git clone git://dev.alpinelinux.org/aports

When the above is done you might be interested in fetching the latest updates.

cd ~

git pull

Create a APKBUILD

You are encouraged to contribute the APKBUILD's that you have made.
Please look at Creating an Alpine package page that describes how you make your own APKBUILD's.