Commit message (Collapse)AuthorAgeFilesLines
* ==== release 3.4.0_rc2 ====v3.4.0_rc2Natanael Copa2019-04-291-1/+1
* abuild-clean: add option to make files writable before cleanupKevin Daudt2019-04-291-0/+3
| | | | | | | | | | | Some projects might leave files which are not writable for the current user. The cleanup process then fails and leaves files / directories behind. This can easily be fixed by making everything writable before removing the files. Add the option 'chmod-clean' which does just that.
* abuild: change word choice in commenttcely2019-04-291-1/+1
* abuild: fix whitespace before EOLNatanael Copa2019-04-291-1/+1
* abuild: provide a default_static() and static() functionsLeo2019-04-291-2/+37
| | | | - Also check for static archives and warn on lack of static subpackage
* newapkbuild: remove obsolete cd statementsIkke2019-04-291-3/+0
| | | | Since `$builddir` is officially supported and abuild automatically cd's to `$builddir`, it does not need to be part of the template anymore.
* Revert "abuild: replace command -v with which to fix build issues"Mike Sullivan2019-04-291-1/+1
| | | | | | This reverts commit 57f2830739e31f9c73d2edaf5103502fbdae6822. fixes the original problem
* Update licenses to spdx format and remove redundant ↵Timothy Legge2019-04-291-9/+4
| | | | directory change
* abuild-fetch: enable curl certificate verificationtcely2019-04-291-2/+2
* APKBUILD.5: sort depends_* descriptionstcely2019-04-291-2/+2
* functions: adjust armhf tripletLuca Weiss2019-04-291-1/+1
| | | | | From what I could find, it was changed to -musleabihf during the Alpine 3.6 release cycle but this function was never updated to reflect that
* Revert "abuild: unset depends for subpackages"Natanael Copa2019-04-251-1/+0
| | | | | | | | | | | | | | | Apparently there are many packages that does soemthing like: subpackages="$pkgname-foo:_foo" _foo() { depends="$depends something-else" } and thus depend on the previous behavior. We need to revert and plan this better. This reverts commit 8fbbffd201a28a06804c7f6d3a2b5cd948c6ce07.
* APKBUILD.5: document depends_* variables for -doc and -openrcSören Tempel2019-04-091-0/+4
* abuild: add depends_libs variable to default_libs()Sören Tempel2019-04-092-0/+3
| | | | | | | | | Other subpackage such as -dev, -doc and even -openrc allow adjusting depends of the subpackage through such a variable. This is, for instance, useful to remove a dependency of the origin package from the -libs subpackage. While at it document it in APKBUILD(5).
* ==== release 3.4.0_rc1 ====v3.4.0_rc1Natanael Copa2019-04-051-1/+1
* get and use pkgdesc from cpan api data if the module has no metadata files ↵Timothy Legge2019-04-031-1/+2
| | | | (returnes unknown)
* abuild: -openrc should not inherit dependstcely2019-04-031-0/+1
* Add default_cleanup_srcdirChloe Kudryavtsev2019-04-031-1/+9
| | | | | | | | | | | | | | | | | | | | In some cases, a simple rm -rf is not sufficent to clean srcdir. One such case is the new go module system, that marks everything as read-only - thus only letting root rm -rf it without a chmod. There is a command intended to clean them - `go clean -modcache`. However, for that to work, GOPATH must be defined and existent. Running chmod for all srcdir cleanups makes no sense, nor does enforcing root, or putting global overrides just for go. This patch allows overriding what happens on `cleanup srcdir`, by overriding cleanup_srcdir, and allows the use of default_cleanup_srcdir. In our go example, it might be used as such: cleanup_srcdir() { go clean -modcache default_cleanup_srcdir }
* Make clean() use cleanup()Chloe Kudryavtsev2019-04-031-3/+2
| | | | Avoid DRY issues, and increase consistency.
* abuild: unset depends for subpackagesNatanael Copa2019-03-211-0/+1
| | | | make sure that subpackages does not inherit main package's depends.
* apkbuild-cpan: use $pkgver in source urlNatanael Copa2019-03-211-1/+1
| | | | replace litteral version string with $pkgver in source url
* apkbuild-cpan: include modules that used to be part of coreNatanael Copa2019-03-211-1/+2
| | | | | | we need to check if a given module currently is a part of core. Modules which have a first_release may have been removed later, for example Module::Build.
* apkbuild-cpan: remove prepare function from APKBUILDNatanael Copa2019-03-211-36/+6
| | | | | | | the generation of Makefile is comparable with running configure, which we normally do in the build() function, not in prepare. also fix some whitespace damamge.
* fix issue with version checkTimothy Legge2019-03-201-2/+2
* fix issues with update, recreate, etcTimothy Legge2019-03-201-7/+12
* Many of setings should come from module not release apiTimothy Legge2019-03-201-7/+8
* Fix for issue with apkbuild-cpan upgradeTimothy Legge2019-03-201-2/+2
* Updates for metacpanTimothy Legge2019-03-201-13/+13
* abuild-sudo: remove unused variableRobert Hencke2019-03-141-1/+1
| | | | This prevents clang from issuing a warning here.
* ==== release 3.3.1 ====v3.3.1Natanael Copa2019-03-051-1/+1
* abuild-tar.static: fix undefined reference errorsOliver Smith2019-03-051-1/+2
| | | | | Link against the same libs as abuild-tar and fix the order of the CC arguments.
* abuild-sign: actually catch errors while signingAndrei Belov2019-03-051-2/+3
* abuild: replace command -v with which to fix build issuesMike Sullivan2019-03-051-1/+1
* Allow forcing of colored outputCarlo Landmeter2019-02-251-1/+3
| | | | | In some cases (ie drone ci) there is no tty available but its still possible to display colors in the webui.
* abuild: add support for pkg-config prefix pcprefixNatanael Copa2019-02-221-2/+12
| | | | | | | | | | | | | | | | | | | | | Fix issue when two -dev packages provides same pkg-config wil but with different versions. For example libressl-dev and openssl-dev both ships libssl.pc and libcrypto.pc, which resulted in automatic provides of pc:libssl and pc:libcrypto. apk would end up picking libressl-dev over openssl-dev for packages that had automatic pc:libssl depends (for example libssl2-dev), when openssl-dev was the one that was used during build. To fix this we add support for a pcprefix so we can set pcprefix="libressl:" in libressl APKBUILD which makes libressl-dev provide pc:libressl:libssl. This is similar to what we do with sonameprefix. We do not yet automatically detect when the prefixed variant should be used so for now we will have to explicitly add libressl-dev. ref #9959
* ==== release 3.3.0 ====v3.3.0Natanael Copa2019-01-231-1/+1
* abuild: replace $0 with $abuild_path, add $forceroot where missingDisassembler2019-01-101-6/+6
* abuild: use pigz to compress control.tar.gz and manpagesNatanael Copa2019-01-101-2/+3
* abuild-sign: fall back to libressl if openssl is missingNatanael Copa2019-01-101-1/+2
| | | | | openssl binary may be missing while migrating system from libressl to openssl. Make sure we can always sign the backage if either is there.
* ==== release 3.3.0_pre2 ====v3.3.0_pre2Natanael Copa2019-01-091-1/+1
* abuild: avoid add depends to itselfNatanael Copa2019-01-091-1/+3
| | | | | | | | | packages should never depend on themselves which does not make sense. This may happen if main package depends on a subpackage, then the subpackages will inherit the global depends and the subpackage ends up depend on itself. Fix abuild to avoid this.
* abuild: fix typoCarlo Landmeter2018-12-021-1/+1
* add multithreaded compressionTiago Ilieve2018-11-081-1/+2
| | | | | | The 'Compressing data' step takes a significant amount of time when packaging software with huge binaries, like Kubernetes. This can certainly be shortened using multithreaded compression, like 'pigz'.
* abuild: print build start, end date and elapsed timeTimo Teräs2018-11-081-1/+5
* abuild-rmtemp: Do not follow symbolic linksSören Tempel2018-10-111-1/+1
| | | | | | | | | | | | | | | Symbolic links might point to files outside of the chroot and thus might delete files outside the chroot. This allows deletion of arbitrary directories on the host from a malicious APKBUILD. Following hard links shouldn't be a problem since hard links (usually) cannot refer to directories and since remove(3) removes the link, not the file it points to it shouldn't cause a problem. I noticed this because alpine-baselayout creates /var/run as a symlink to /run. Therefore causing /run to be deleted on the host when using abuild-rmtemp which in turn causes a bunch of software to no longer function properly (including OpenRC).
* ==== release 3.3.0_pre1 ====v3.3.0_pre1Natanael Copa2018-10-031-1/+1
* abuild: run build actions via runpartNatanael Copa2018-10-031-11/+5
| | | | So we make sure chdir $builddir happens when it should.
* abuild: do not run check in fakeroot by defaultNatanael Copa2018-10-032-10/+9
| | | | | | | | | Only run check in fakeroot if options="checkroot" is set. This makes options="!checkroot" the default. I expect most checks work as non-root, and if a testsuite requires root, it will likely fail in fakeroot too. Fakeroot has also shown lower performance for parallel builds.
* abuild: print version of built package earlyNatanael Copa2018-10-031-1/+1
| | | | | instead of printing abuild version, print package version. This is to avoid confuse the abuild version with the package version.
* abuild: chdir to $builddir if it existsNatanael Copa2018-10-031-0/+6
| | | | chdir to $builddir before running prepare, build, package or check.