Otherwise we might end up purging more packages than expected if an
APKBUILD has syntax errors

Some packages like gcc-gnat needs bootstrapping. We need to allow
circular makedepends so we can specify gcc-gnat as makedepends for gcc.

fixes bug introduced with c6b0de32 (abuild: add makedepends_build and
makedepends_host for crosscompile)

to detect if we cross compile

For better crosscompile support

allow user specify if they want uninstall deps, remove srcdir and/or
pkgdir on failure or success.

We introduce CLEANUP and ERROR_CLEANUP config options in
/etc/abuild.conf. Valid values are: pkgdir srcdir deps.

seems like configure thinks we are crosscompiling unless we set CC when
--build and --host are specified.

this is to catch bugs in abuild itself early

it wrongly scanned /lib instead of $datadir/lib, causing bad things to
happen when scanning provides

Timo Teräs authored 11 years ago and Natanael Copa committed 11 years ago

its only arm that needs it

instead let apkbuilds use --host and --build

Timo Teräs authored 11 years ago and Natanael Copa committed 11 years ago

and exit with error if not

This reverts commit 4234a10e.

We will not use config.guess. Instead we will use --build and --host
everywhere.

instead, provide 'update_config_sub' and let aports that needs replace
config.sub call it.

we want be able to run build and rootpkg separately. so you can stop
in the process, fix things, and then continue with 'abuild rootpkg' to
generate the package manually.

If some package fails, then stop processing the rest. This is so we
don't risk test build the rest for the packages against wrong lib.

For example, if 'abump libfoo-2.0 foo-2.0' fails on libfoo, we don't
want testbuild foo-2.0, which might end with success against libfoo-1.

We also echo the list of packages that was not bumped, so its easy to
copy/paste next run.

Use a global var for last_commit so we dont need call git for every
subpackage

For example, to mask out musl, add:
options="!libc_musl"

We need set it in global scope as we need it even if we have not called
sanitycheck

we better fix the affected apkbuilds