Skip to content
Snippets Groups Projects
  1. Jan 26, 2021
  2. Jun 13, 2019
  3. Dec 30, 2017
    • Jakub Jirutka's avatar
      [various]: unify names of licenses according to SPDX · 63f5e7d2
      Jakub Jirutka authored
      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/
      63f5e7d2
  4. Oct 19, 2017
  5. Aug 25, 2016
    • Carlo Landmeter's avatar
      testing/[multiple]: move unmaintained packages · b6af1e02
      Carlo Landmeter authored
      This moves all packages from testing to unmaintained which have not been
      updated for atleast 6 months. If you are affected by this commit please follow
      this proceddure:
      
      * make sure your packages build on all architectures
      * move your pacakge(s) back to testing
      * if you want to keep this package and can maintain it (or find somebody to
        maintain it for you) for a minimum of 6 months ask it to be moved to community
      b6af1e02
  6. Sep 10, 2015
  7. Nov 20, 2013
  8. Oct 30, 2012
  9. Jul 01, 2011
  10. Dec 21, 2010
Loading