...
 
Commits (30263)

Too many changes to show.

To preserve performance only 1000 of 1000+ files are displayed.

---
kind: pipeline
name: edge-x86
clone:
disable: true
platform:
os: linux
arch: amd64
steps:
- name: build
image: alpinelinux/alpine-drone-ci:edge-x86
commands:
- linux32 build.sh
environment:
GH_TOKEN:
from_secret: github_token
pull: always
trigger:
event:
- pull_request
---
kind: pipeline
name: edge-x86_64
clone:
disable: true
platform:
os: linux
arch: amd64
steps:
- name: build
image: alpinelinux/alpine-drone-ci:edge-x86_64
commands:
- build.sh
environment:
GH_TOKEN:
from_secret: github_token
pull: always
trigger:
event:
- pull_request
---
kind: pipeline
name: edge-aarch64
clone:
disable: true
platform:
os: linux
arch: arm64
steps:
- name: build
image: alpinelinux/alpine-drone-ci:edge-aarch64
commands:
- build.sh
environment:
GH_TOKEN:
from_secret: github_token
pull: always
trigger:
event:
- pull_request
---
kind: pipeline
name: edge-armhf
clone:
disable: true
platform:
os: linux
arch: arm
steps:
- name: build
image: alpinelinux/alpine-drone-ci:edge-armhf
commands:
- build.sh
environment:
GH_TOKEN:
from_secret: github_token
pull: always
trigger:
event:
- pull_request
---
kind: pipeline
name: edge-armv7
clone:
disable: true
platform:
os: linux
arch: arm
steps:
- name: build
image: alpinelinux/alpine-drone-ci:edge-armv7
commands:
- build.sh
environment:
GH_TOKEN:
from_secret: github_token
pull: always
trigger:
event:
- pull_request
R-main: /main
R-community: /community
R-testing: /testing
R-unmaintained: /unmaintained
R-non-free: /non-free
R-aports: ["/.github", "/.githooks", "/scripts"]
skipCreatedBefore: 2020-01-01
# Close issues and pull requests
close: true
# Lock issues and pull requests
lock: false
pulls:
comment: >
This repository does not accept Pull Requests (PR) anymore.
Development has moved to https://gitlab.alpinelinux.org/alpine/aports
Please signup and create a Merge Request (MR) instead.
Sorry for the inconvenience caused.
lock: true
<!-- Attention Required
Dear Contributor,
Alpine Linux has moved its development to its own GitLab instance located at
https://gitlab.alpinelinux.org/alpine. To submit your code changes for aports
please create an account on our GitLab instance by registering or logging in
with your GitHub account and submit it as a Merge Request (also known as a MR).
This GitHub repository will be kept operational as a git mirror. Pull request
made in this repository will automatically be closed by our GitHub bot.
Sorry for the inconvenience and happy hacking!
-->
Run `git config -e` and add the block below then run `git fetch --all` to update all the GitHub pull request branches.
```
[remote "github"]
url = https://github.com/alpinelinux/aports.git
fetch = +refs/heads/*:refs/remotes/github/*
fetch = +refs/pull/*:refs/remotes/github/pr/*
```
After you have done this you can merge / squash / rebase / cherry-pick from the command line.
For example, `git rebase master github/pr/XXX/head; git checkout master` would migrate all the commits from PR #XXX.
You can then push the results back to the "origin" remote which should be the official Alpine Linux aports repository.
# Configuration for probot-stale - https://github.com/probot/stale
# Number of days of inactivity before an Issue or Pull Request becomes stale
daysUntilStale: 180
# Number of days of inactivity before a stale Issue or Pull Request is closed.
# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
daysUntilClose: 7
# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
exemptLabels:
- S-WIP
# Set to true to ignore issues in a project (defaults to false)
exemptProjects: false
# Set to true to ignore issues in a milestone (defaults to false)
exemptMilestones: false
# Label to use when marking as stale
staleLabel: S-stale
# Comment to post when marking as stale. Set to `false` to disable
markComment: >
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
# Comment to post when removing the stale label.
# unmarkComment: >
# Your comment here.
# Comment to post when closing a stale Issue or Pull Request.
# closeComment: >
# Your comment here.
# Limit the number of actions per hour, from 1-30. Default is 30
limitPerRun: 30
# Limit to only `issues` or `pulls`
only: pulls
# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
pulls:
daysUntilStale: 180
markComment: >
This pull request has been automatically marked as stale because it has not
had activity in the last 180 days. It will be closed in 7 days if no further
activity occurs. Thank you for your contributions.
# issues:
# exemptLabels:
# - confirmed
daysUntilStale: 60
daysUntilClose: 14
staleLabel: S-stale
exemptLabels:
- S-help-wanted
- S-needs-review
- S-ready
- S-waiting-maintainer-review
- S-WIP
- T-backport-it
- T-security
markComment: |
Sorry to bother you, but we noticed there has't been any activity on this
pull request for 60 days. Because we have to deal with a lot of pull
requests, we use this stupid bot to automatically mark it as stale.
If you still want this PR to be merged, you can do the following:
1. Rebase the PR on the latest master.
2. Apply any feedback you might have received.
3. Make sure the package builds without issues in CI.
4. If the PR is waiting on us, feel free to ping one of us here or on IRC.
If you are no longer interested in this PR, you don't have to do anything.
The PR will automatically be closed in 14 days.
closeComment: >
This pull request has been automatically closed.
stages:
- lint
- build
variables:
GIT_STRATEGY: clone
GIT_DEPTH: "50"
default:
# Make sure master points to the correct upstream commit
before_script:
- >
git fetch -nq $CI_MERGE_REQUEST_PROJECT_URL
+refs/heads/$CI_MERGE_REQUEST_TARGET_BRANCH_NAME:refs/heads/$CI_MERGE_REQUEST_TARGET_BRANCH_NAME
lint:
stage: lint
image: alpinelinux/apkbuild-lint-tools:latest
script:
- changed-aports $CI_MERGE_REQUEST_TARGET_BRANCH_NAME | lint
allow_failure: true
only:
- merge_requests
tags:
- docker-alpine
- x86_64
.build:
stage: build
image: alpinelinux/alpine-gitlab-ci:latest
script:
- build.sh
- cp -ar ~/packages packages/
- mkdir -p keys
- cp ~/.abuild/*.rsa.pub keys/
artifacts:
paths:
- packages/
- keys/
expire_in: 1 day
only:
- merge_requests
build-x86_64:
extends: .build
artifacts:
name: MR${CI_MERGE_REQUEST_ID}_x86_64
tags:
- docker-alpine
- ci-build
- x86_64
build-x86:
extends: .build
image:
name: alpinelinux/alpine-gitlab-ci:latest-x86
entrypoint: ["linux32", "sh", "-c"]
artifacts:
name: MR${CI_MERGE_REQUEST_ID}_x86
tags:
- docker-alpine
- ci-build
- x86
build-s390x:
extends: .build
artifacts:
name: MR${CI_MERGE_REQUEST_ID}_s390x
tags:
- docker-alpine
- ci-build
- s390x
build-ppc64le:
extends: .build
artifacts:
name: MR${CI_MERGE_REQUEST_ID}_ppc64le
tags:
- docker-alpine
- ci-build
- ppc64le
build-aarch64:
extends: .build
artifacts:
name: MR${CI_MERGE_REQUEST_ID}_aarch64
tags:
- docker-alpine
- ci-build
- aarch64
build-armv7:
extends: .build
image:
name: alpinelinux/alpine-gitlab-ci:latest-armv7
entrypoint: ["linux32", "sh", "-c"]
artifacts:
name: MR${CI_MERGE_REQUEST_ID}_armv7
tags:
- docker-alpine
- ci-build
- armv7
......@@ -2,4 +2,11 @@ Timo Teräs <timo.teras@iki.fi>
Natanael Copa <ncopa@alpinelinux.org> <natanael.copa@gmail.com>
Natanael Copa <ncopa@alpinelinux.org> <ncopa@ncopa-laptop.localdomain>
Natanael Copa <ncopa@alpinelinux.org> <ncopa@alpine-netbook.(none)>
Jean-Louis Fuchs <ganwell@fangorn.ch> <jean-louis.fuchs@adfinis-sygroup.ch>
Kevin Daudt <kdaudt@alpinelinux.org> <ops@ikke.info>
Lucas Ramage <ramage.lucas@protonmail.com> <oxr463@gmx.us>
Lucas Ramage <ramage.lucas@protonmail.com> <ramage.lucas@openmailbox.org>
Lucas Ramage <ramage.lucas@protonmail.com> <lramage@star2star.com>
<eu@eju.no> <eivind@uggedal.com>
Oliver Smith <ollieparanoid@postmarketos.org> <ollieparanoid@bitmessage.ch>
Bart Ribbers <bribbers@disroot.org> <bart.ribbers@openmailbox.org>
......@@ -93,7 +93,7 @@ done
printf '\n----\n'
if [ -n "$successful_pkgs" ]; then
print -s1 -c2 "Successfully build packages:$successful_pkgs\n"
print -s1 -c2 "Successfully built packages:$successful_pkgs\n"
fi
if [ -n "$failed_pkgs" ]; then
die "Failed to build packages:$failed_pkgs"
......
# Policy for APKBUILDs
This documents defines a policy for writing APKBUILDs.
# Standard selection
APKBUILDs are POSIX shell scripts as defined in [POSIX.1-2017 Volume 3]
[POSIX.1-2017 volume 3]. Additionally, the following extensions are
supported:
1. The `local` keyword for introducing variables local to a function is
supported, it is briefly documented in the [bash manual][bash functions].
2. Non-POSIX [parameter extensions][POSIX.1-2017 parameter expansion]
are supported. This includes: Substring expansions (e.g.
`${var:offset:length}`) and Replacement expansions (e.g.
`${var/pattern/string}`). The [bash manual][bash expansion]
contains further information on these two expansions.
**NOTE:** `busybox ash` is currently used to evaluate APKBUILDs since it
supports additional POSIX shell extensions your APKBUILD might be
evaluated correctly even if it is not confirming to this policy
document.
# Shell Style Considerations
<!--
This should be in conformance with most existing APKBUILDs
Structure and content inspired by Google Shell Style Guide.
-->
## Formatting
### Indention
Indent with tabs, don't use spaces. Avoid whitespaces.
### Line Length
Maximum line length is 80 characters, this should be considered a
recommendation and not a string requirement which must be followed at
all costs. Most notably, automatically generated parts (e.g. by `abuild
checksum`) are except from this rule.
### Compound Statements
Put `; do` and `; then` on the same line as the `while`, `for` or `if`.
### Function Declarations
* Always put the function name, the parenthesis and the curly brackets
on the same line.
* Don't use spacing between function name and parenthesis.
* Do use spacing between function parenthesis and curly brackets.
### Case statement
* Don't indent alternatives.
* A one-line alternative needs a space after the close parenthesis of the pattern and before the `;;`.
* End the last case with `;;`.
### Variable expansion
* Use `${var}` over `$var` only when it is strictly necessary. Meaning:
Only if the character following the [variable name][POSIX.1-2017 definition name]
is an underscore or an alphanumeric character.
### Quoting
* Always quote string literals (exceptions are assigning `pkgname` and
`pkgver`, more on this below).
* Always quote variables, command substitutions or shell meta characters
when used in strings. Prefer `"$var"/foo/bar` over `"$var/foo/bar"`.
* Never quote literal integers.
## Features
### Command Substitution
* Always use `$()` instead of backticks.
### Test and [
* Prefer `[` over `test(1)`.
## Naming Conventions
### Function Names
* Lower-case, with underscores to separate words. Prefix all helper
functions with an underscore character.
### Variable Names
* Lower-case, with underscores to separate words. Prefix all
non-metadata variables with an underscore character.
### Use Local Variables
* Declare function-specific variables with the `local` keyword.
## Calling Commands
### Command Substitutions and Global Variables
* Avoid command Substitutions in global variables, use parameter
expansions instead.
### Return Values
* APKBUILDs are executed with `set -e`, explicit `|| return 1`
statements must not be used.
## Comments