aports - Main aports tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	community/elixir: upgrade to 1.6.5	gmile	2018-05-08	1	-2/+2
\|
*	community/elixir: fix checksums again	Jakub Jirutka	2018-03-31	1	-1/+0
\| \| \| \|	I'm deeply sorry, I was too rashed. :(
*	community/elixir: fix checksum	Jakub Jirutka	2018-03-31	1	-1/+1
\| \| \| \|	Mistake in rebasing PR.
*	community/elixir: upgrade to 1.6.4	gmile	2018-03-31	2	-87/+2
\|
*	community/elixir: add note about patch removal	gmile	2018-03-16	1	-0/+1
\|
*	community/elixir: fix TODO	gmile	2018-03-16	1	-4/+1
\|
*	community/elixir: fix build under Erlang 20.3	gmile	2018-03-16	2	-1/+87
\|
*	community/elixir: upgrade to 1.6.3	gmile	2018-03-11	1	-2/+2
\|
*	community/elixir: upgrade to 1.6.2	gmile	2018-02-28	1	-2/+2
\|
*	community/elixir: upgrade to 1.6.1	gmile	2018-02-13	1	-2/+2
\|
*	community/elixir: disable check on aarch64	Sören Tempel	2018-01-20	1	-0/+4
\|
*	community/elixier: add check	Sören Tempel	2018-01-20	2	-2/+28
\|
*	community/elixir: upgrade to 1.6.0	gmile	2018-01-20	1	-5/+3
\|
*	[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/elixir: upgrade to 1.5.3	gmile	2017-12-27	1	-2/+2
\|
*	community/elixir: upgrade to 1.5.2	gmile	2017-10-03	1	-2/+2
\|
*	community/elixir: upgrade to 1.5.1	gmile	2017-08-05	1	-3/+2
\|
*	community/elixir: upgrade to 1.5.0	gmile	2017-07-28	1	-2/+2
\|
*	community/elixir: upgrade to 1.4.5	Roberto Oliveira	2017-07-07	1	-2/+2
\|
*	community/elixir: upgrade to 1.4.4	Francesco Colista	2017-06-16	1	-4/+5
\|
*	community/elixir: upgrade to 1.4.2	Mario Mainz	2017-04-04	1	-4/+2
\|
*	community/elixir: upgrade to 1.4.1	Pavel Vesnin	2017-02-08	1	-4/+4
\|
*	community/elixir: upgrade to 1.3.4	Daniel Sabogal	2016-11-04	1	-4/+4
\|
*	community/elixir: fix indentation in abuild	Jakub Jirutka	2016-08-16	1	-3/+2
\|
*	community/elixir: upgrade to 1.3.2	Aaron Jensen	2016-08-16	1	-4/+4
\|
*	community/elixir: upgrade to 1.3.1	Marlus Saraiva	2016-07-12	1	-17/+8
\|
*	community/elixir: upgrade to 1.2.6	Francesco Colista	2016-06-07	1	-4/+4
\|
*	community/elixir: upgrade to 1.2.5	Marlus Saraiva	2016-05-04	1	-4/+4
\|
*	main/elixir: new upstream version 1.2.4	Christian Kampka	2016-04-02	1	-4/+4
\|
*	community/elixir: Update to 1.2.1	Marlus Saraiva	2016-01-19	1	-4/+4
\|
*	community/elixir: move from main	Natanael Copa	2015-10-15	1	-0/+40