Add a wrapper .ci/wiki.sh, that pmbootstrap ci can run and use it in
gitlab-ci.yml. Add a .ci/lib/gitlab_prepare_ci.sh script that makes a
user available with sudo, as expected by the pmbootstrap ci compatible
scripts. Set up binfmt_misc too while at it, it will be needed for
running pmbootstrap.

The next patches will adjust the rest of the CI scripts and move the old
scripts in the .ci/lib dir, so only the scripts that should be called
directly are in the .ci dir.

Related: https://postmarketos.org/pmb-ci

Clayton Craft authored 3 years ago and Dylan Van Assche committed 3 years ago

When using abuild to update checksums and other things manually in pmaports,
it creates a src/ dir in the package dir which should not be commited.

for when you use `abuild unpack prepare` to investigate
the package sources and other uses of abuild.

Martijn Braam authored 5 years ago and Oliver Smith committed 5 years ago

This allows for having untracked packages in the aports directory in a
subdirectory prefixed by "custom-".

Copy all test cases from the pmbootstrap repository, that are actually
testing the aports. They were all adjusted to work nicely in this
repository, together with a brand new set of gitlab-ci configs.

This also includes the changes from this merge request, that had a
better detection of changed packages:
<https://gitlab.com/postmarketOS/pmbootstrap/merge_requests/1621>