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/ | ||||
* | community/cargo: fix compatibility with libressl 2.6.3 | Jakub Jirutka | 2017-11-13 | 4 | -10/+238 |
| | | | | See https://github.com/sfackler/rust-openssl/pull/759 | ||||
* | community/cargo: re-enable | Jakub Jirutka | 2017-11-12 | 1 | -1/+1 |
| | |||||
* | community/cargo: rebuild against libressl-2.6 | Natanael Copa | 2017-11-09 | 1 | -2/+2 |
| | |||||
* | community/cargo: build with newer openssl crate for LibreSSL compat | Jakub Jirutka | 2017-11-08 | 2 | -3/+128 |
| | |||||
* | community/cargo: use statically linked binary for bootstrapping | Jakub Jirutka | 2017-11-08 | 1 | -3/+4 |
| | | | | | | | | | Rust incorrectly links so libs with version suffix instead of their symlinks without suffix. For example: 0x000000000000000e (SONAME) Library soname: [libgit2.so.25] Consequences are obvious. This needs to be fixed in Rust. | ||||
* | community/cargo: upgrade to 0.22.0 | Jakub Jirutka | 2017-10-31 | 3 | -54/+62 |
| | |||||
* | Revert "community/cargo: upgrade to 0.22.0" | William Pitcock | 2017-10-30 | 3 | -47/+58 |
| | | | | | | | | | | This change causes the package to be unbuildable without manual intervention, which violates policy. Reverting the change is theoretically harmless, as the old cargo has not been removed from the archive. This reverts commit c6e8dbdbd42fc99d297045cf6bd0e3d9474e53ad. | ||||
* | community/cargo: upgrade to 0.22.0 | Jakub Jirutka | 2017-10-28 | 3 | -58/+47 |
| | | | | | | | | | | | We don't download prebuilt cargo binary anymore, mainly because that URL on S3 doesn't work anymore. They have moved it *again* and https://static.rust-lang.org/dist/ still does not contain musl binaries. However, we need cargo to build rust, so when building cargo, we must already have cargo anyway. And cargo cannot be built without rust. | ||||
* | community/cargo: move from testing | Jakub Jirutka | 2017-05-17 | 2 | -0/+161 |