it contains a list with all triggers for all subpackages.

separate trigger script from path list with '='
separate paths in path list with ':'

example:

pkgname="foo"
subpackages="foo-libs foo-dev"
triggers="foo.trigger=/usr:/usr/lib/foo
	foo-libs.trigger=/usr:/usr/share/foo"

We need to list all install scripts in $install rather than specify it
in subpackage

we check early that suffix is valid and that we have a matching
pkgname or subpackage

- provide a handle with aports.new(dir)
- provide foreach() helper functions

Kiyoshi Aman authored 13 years ago and Timo Teräs committed 13 years ago

so we get arch set properly

Don't update if it's unknown, and fix the error message.

Based on Aerdan's original work, this is a perl utility that
interacts with CPAN which can create and update APKBUILDs with
proper metadata info.

to help make perl-* packages

We don't really need to see what packages gets uninstalled, but error
messages might be nice to see. So we are quiet when uninstalling.

only main package has the trigger

we need set the $CARCH in the package destination
needs also to be passed over for recursive action

We no require apk-tools-2.1

Conflicts:
	Makefile

apk-tools-2.0's apk index will not show the arch so we need to use
tar to find arch if we have old apk. We prefer use apk index since
it will only read first block of file, regardless size, while tar
will read entire file. Reading entire file is slow if file is big.

So we check apk --version and use tar if needed, and apk index if
possible.