kunkku/aports - kunkku's aports repo

	Commit message (Collapse)	Author	Age	Files	Lines
*	testing/biblatex: upgrade to 3.11	Francesco Colista	2018-02-22	1	-2/+2
\|
*	[various]: unify names of licenses according to SPDX	Jakub Jirutka	2017-12-30	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This commit updates $license variable in all APKBUILDs to comply with short names specified by SPDX version 3.0 [1] where possible. It was done using find-and-replace method on substrings inside $license variables. Only license names were updated, not "expressions" specifying relation between the licenses (e.g. "X and Y", "X or Y", "X and (Y or Z)") or exceptions (e.g. "X with exceptions"). Many licenses have a version or multiple variants, e.g. MPL-2.0, BSD-2-Clause, BSD-3-Clause. However, $license in many aports do not contain license version or variant. Since there's no way how to infer this information just from abuild, it were left without the variant suffix or version, i.e. non SPDX compliant. GNU licenses (AGPL, GFDL, GPL, LGPL) are especially complicated. They exist in two variants: -only (formerly e.g. GPL-2.0) and -or-later (formerly e.g. GPL-2.0+). We did not systematically noted distinguish between these variants, so GPL-2.0, GPL2, GPLv2 etc. may mean GPL-2.0-only or GPL-2.0-or-later. Thus GNU licenses without "+" (e.g. GPL2+) were left without the variant suffix, i.e. non SPDX compliant. Note: This commit just fixes format of the license names, no verification has been done if the specified license information is actually correct! [1]: https://spdx.org/licenses/
*	testing/biblatex: upgrade to 3.10	Francesco Colista	2017-12-21	1	-2/+2
\|
*	testing/biblatex: upgrade to 3.9	Francesco Colista	2017-11-26	1	-2/+2
\|
*	testing/biblatex: fix checksum	Jakub Jirutka	2017-11-19	1	-1/+1
\| \| \| \| \| \|	Upstream recreated tag v3.8 two weeks ago. According to history of this APKBUILD, there was tag v3.8 in January and the sha512sum in the APKBUILD is of the original tag, not the new one.
*	testing/biblatex: upgrade to 3.8	Francesco Colista	2017-11-19	1	-5/+2
\|
*	Revert "testing/biblatex: upgrade to 3.8"	Francesco Colista	2017-01-26	1	-4/+4
\| \| \| \| \| \|	This reverts commit b70ffd376d82148c82a4074ff06e81272deb380a. Biblatex is related to biber to work, but biber is not yet tagged to 2.8 (which is supposed to work with this versionof biblatex)
*	testing/biblatex: upgrade to 3.8	Francesco Colista	2017-01-24	1	-4/+4
\|
*	testing/biblatex: upgrade to 3.7	Francesco Colista	2017-01-04	1	-4/+4
\|
*	testing/biblatex: fixed checksum,reverted pkgrel to 0	Francesco Colista	2016-09-21	1	-4/+4
\|
*	testing/biblatex: bump pkgrel	Francesco Colista	2016-09-21	1	-1/+1
\|
*	testing/biblatex: new aport. Fixes #6203	Francesco Colista	2016-09-21	1	-0/+29