Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | [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/pylint:added missing dependencies. Close #8110 | Francesco Colista | 2017-11-26 | 1 | -4/+4 |
| | |||||
* | testing/pylint: upgrade to 1.7.4 | Roberto Oliveira | 2017-10-06 | 1 | -5/+3 |
| | |||||
* | testing/pylint: rebuild against new version of python3 | Ćukasz Jendrysik | 2017-02-18 | 1 | -1/+1 |
| | |||||
* | testing/pylint: upgrade to 1.6.4 and enable py3 | Fabian Affolter | 2016-12-27 | 1 | -10/+30 |
| | |||||
* | [various] rename python executable in APKBUILDs to python2 | Jakub Jirutka | 2016-10-26 | 1 | -2/+2 |
| | |||||
* | [various] rename dependency python to python2 | Jakub Jirutka | 2016-10-26 | 1 | -1/+1 |
| | |||||
* | [various] rename dependency python-dev to python2-dev | Jakub Jirutka | 2016-10-26 | 1 | -1/+1 |
| | |||||
* | testing/pylint: fix build | Carlo Landmeter | 2016-08-28 | 1 | -10/+3 |
| | |||||
* | testing/*: change source URL pypi.python.org to files.pythonhosted.org | Jakub Jirutka | 2016-07-08 | 1 | -1/+1 |
| | | | | See https://bitbucket.org/pypa/pypi/issues/438/backwards-compatible-un-hashed-package#comment-27734791 | ||||
* | testing/pylint: upgrade to 1.4.3 | Fabian Affolter | 2015-03-29 | 1 | -4/+4 |
| | |||||
* | testing/pylint: fix checksums | Natanael Copa | 2015-03-11 | 1 | -3/+3 |
| | |||||
* | testing/pylint: upgrade to 1.4.1 | Fabian Affolter | 2015-03-11 | 1 | -1/+1 |
| | |||||
* | testing/pylint: upgrade to 1.4.0 | Fabian Affolter | 2014-11-27 | 1 | -5/+5 |
| | |||||
* | testing/pylint: upgrade to 1.3.0 | Fabian Affolter | 2014-08-23 | 1 | -5/+5 |
| | |||||
* | testing/pylint: upgrade to 1.2.1 | Fabian Affolter | 2014-07-07 | 1 | -4/+4 |
| | |||||
* | testing/pylint: upgrade to 1.1.0 | Fabian Affolter | 2014-03-11 | 1 | -7/+7 |
| | |||||
* | testing/pylint: deps update | Fabian Affolter | 2013-09-17 | 1 | -3/+3 |
| | |||||
* | testing/pylint: upgrade to 1.0.0 | Fabian Affolter | 2013-09-08 | 1 | -4/+4 |
| | |||||
* | testing/pylint: upgrade to 0.28.0 | Fabian Affolter | 2013-06-15 | 1 | -2/+4 |
| | |||||
* | testing/pylint: upgrade to 0.26.0 | Fabian Affolter | 2013-01-08 | 1 | -2/+2 |
| | |||||
* | testing/pylint: upgrade to 0.25.2 | Fabian Affolter | 2012-09-21 | 1 | -2/+2 |
| | |||||
* | testing/pylint: upgrade to 0.25.1 | Fabian Affolter | 2012-05-20 | 1 | -2/+2 |
| | |||||
* | Initial APKBUILD for pylint | Fabian Affolter | 2011-12-03 | 1 | -0/+34 |
Package description: Pylint is a python tool that checks if a module satisfies a coding standard. Pylint is similar to PyChecker but offers more features, like checking line-code's length, checking if variable names are well-formed according to your coding standard, or checking if declared interfaces are truly implemented, and much more. The big advantage with Pylint is that it is highly configurable, customizable, and you can easily write a small plugin to add a personal feature. |