Those are needed when linking to the lib and not during runtime.

Having those in the -dev package makes it easier to allow different
versions of same libs to be installed side-by-side.

based on patch from Andrew Manison. Thanks!

and make sure those options are passed over when building recursively

Based on patch from Andrew Manison. Thanks!

We want build the toolchain and build tools first

we need strip all '<>=' chars not only last

speeds up abuild -R a bit

To avoid confusing with the /etc/apk/cache

its needed for bumping pkgrel with sed and similar

so we can do: APK=apk.static abuild ....

we only enter dependencies dirs in same repo

When building with crosscompile to bootstrap a new target it might
be handy to not include the dependencies etc.

This avoids confusion when abuild picks dependencies from testing
when building main.

This option is normally used for bootstrapping a build env. Chances are big
that apk-tools is not around.

to make life easier for volatile packages

override with -F

We also make sure we source the APKBUILD when we are in the directory
holding the APKBUILD file. Some of the packages sources others
with relative references. (for example kernel 3rd party packages)

try keep code in abuild cleaner by moving out creation of new apkbuild
to separate script.

prepare is run before build(). this allows uses to do patching before
configuring and building in a separate step.

fakeroot seems do some kind of locking which kills performance on
multicores processors. We can run "make" and "make install" in 2 steps
with only hte latter in fakeroot.

and install scripts should not be in $source