aboutsummaryrefslogtreecommitdiffstats
path: root/community/geany-plugins
Commit message (Collapse)AuthorAgeFilesLines
* community/geany-plugins: upgrade to 1.35Kevin Daudt2019-05-151-2/+2
|
* community/geany-plygins: disable pluginsKevin Daudt2019-05-151-5/+9
| | | | | | | | | | | | | The following plugins are not being built because the rely on GTK+2.0, while geany depends on GTK+3.0: - geanypy - multiterm - scope Disable the subpackages for now. Closes GH-7883
* community/geany-plugins: upgrade to 1.34Roberto Oliveira2018-12-251-2/+4
| | | | Add "Vimode" plugin introduced in this version
* community/geany-plugins: upgrade to 1.33Roberto Oliveira2018-06-171-4/+4
| | | | plugin GeanyLaTeX was renamed to latex
* [various]: unify names of licenses according to SPDXJakub Jirutka2017-12-301-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/geany-plugins: upgrade to 1.32Carlo Landmeter2017-11-221-8/+17
|
* community/*: fix homepage url and source from http:// to https://Jakub Jirutka2017-11-191-2/+2
| | | | | | | Most of these updates is based on data from https://repology.org/, detection based on permanent redirect from http:// to https://. $source urls are updated when they contain $url as substring.
* community/geany-plugins: Add dependency packageBreno Leitao2017-05-031-1/+1
| | | | | | | | | | | | | | | Geany-plugins FTBFS if python2-dev package is not installed. This is the message that appears during the build process: Could not link test program to Python. Maybe the main Python library has been installed in some non-standard library path. If so, pass it to configure, via the LIBS environment variable. Example: ./configure LIBS="-L/usr/non-standard-path/python/lib" ============================================================================ ERROR! You probably have to install the development version of the Python package for your distribution. The exact name of this package varies among them. ============================================================================
* community/geany-plugins: upgrade to 1.30Natanael Copa2017-03-291-15/+20
|
* community/geany-plugins: rebuild against gpgme-1.8.0Natanael Copa2017-02-161-1/+1
|
* community/geany-plugins: upgrade to 1.27Natanael Copa2016-03-291-4/+4
|
* community/geany-plugins: upgrade to 1.26Natanael Copa2015-11-161-4/+4
|
* community/geany-plugins: move from testingNatanael Copa2015-11-161-0/+140