So we can fish out the maintainer from given aport

if there are an APKBUILD in current dir, then use ../ as repodir.
Otherwise, use cwd as repodir.

Introduces requirement of lua-filesystem

This might happen if package name appears as a dependency but there
are no apkbuild for it.

we might have '.' in pkgname as in gtk+2.0

To be allowed to keep the .la files you need to add 'libtool' to
$options

This buildtype is when there is a simple Makefile only.

We call make as well as needed so build_* is better function name.

Fabian Affolter authored 13 years ago and Natanael Copa committed 13 years ago

With -q ('-q' for the moment, please change that) a template
APKBUILD file for a python module is created. 'depends' and
'makedepends' are filled with standard values.

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