aports - Main aports tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	community/monitoring-plugins: rebuild against mariadb-connector-c	Natanael Copa	2018-03-26	2	-4/+104
\|
*	[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/
*	community/monitoring-plugins: ping from iputils does not support -4 and -6 flags	Francesco Colista	2017-11-14	1	-3/+3
\|
*	community/monitoring-plugins: set the right /bin/ping path	Francesco Colista	2017-11-10	1	-3/+3
\|
*	community/monitoring-plugins: fixed typo in configure	Francesco Colista	2017-11-07	1	-3/+2
\|
*	community/monitoring-plugins: added iputils as dependency, updated ping ↵	Francesco Colista	2017-11-07	1	-2/+5
\| \| \| \|	command and added ping6
*	community/monitoring-plugins: add ping command with correct parameters to ↵	Francesco Colista	2017-11-03	1	-10/+8
\| \| \| \|	make check_ping work
*	community/monitoring-plugins: fix build	Natanael Copa	2017-04-18	2	-24/+6
\| \| \| \| \| \| \| \| \| \|	the configure script requres that --with-perl has a valid patch to perl upstream bug report: https://github.com/monitoring-plugins/monitoring-plugins/issues/1480 If --with-pgsql has no path specified, then will things go bad too. upstream bug report: https://github.com/monitoring-plugins/monitoring-plugins/issues/1484
*	community/monitoring-plugins: disable on all archs	Natanael Copa	2017-04-11	2	-10/+24
\| \| \| \| \|	bug in the configure script will fill up the buildservers disk https://github.com/monitoring-plugins/monitoring-plugins/issues/1480
*	community/monitoring-plugins: Disable building on ppc64le	Breno Leitao	2017-04-08	1	-1/+1
\| \| \| \| \|	Disabling this package temporarily because I am not able to reproduce the buildlog issue on my machine.
*	community/monitoring-plugins: build fix	William Pitcock	2017-04-07	1	-1/+1
\|
*	community/monitoring-plugins: fix build on ppc64le	William Pitcock	2017-04-07	1	-0/+6
\|
*	community/monitoring-plugins: ugprade to 2.2	Francesco Colista	2016-12-02	1	-18/+8
\|
*	community/monitoring-plugins: rebuild against libressl	Natanael Copa	2016-10-10	1	-2/+2
\|
*	community/monitoring-plugins: moved from testing	Francesco Colista	2016-04-22	1	-0/+59