Commits on Source (4)
-
Clayton Craft authored
Here's the problem: Imagine a queue with 2 packages in it, the 1st package uses crossdirect and the second uses cross-native. When building the 1st package, pmb will configure the native chroot for crossdirect as expected. When it gets to the 2nd package, the chroot env/config might not be appropriate for actually doing a native cross compile. This re-inits the cross compiler stuff if the cross compile method changes while processing the queue. Another approach that might solve this problem is to not re-use chroots when building packages... I didn't think this was a good way to go because it would greatly increase runtime (having to recreate chroots multiple times)
-
Oliver Smith authored
It is not needed to run the linter as root, so don't do it. This is probably a leftover from early days pmbootstrap, where pmaports.git wasn't chowned by the user running pmbootstrap.
-
Oliver Smith authored
The output of apkbuild-lint is hard to spot among other log messages from pmbootstrap, because it is not colorized. Add "*** apkbuild-lint output ***"" before and after the output of apkbuild-lint, so we get a standing out message in green around the apkbuild-lint output.
-
Oliver Smith authored
Now that we have moved the kconfigcheck configuration into pmaports branches via kconfigcheck.toml, it is time to get rid of the hardcoded list of valid "pmb:kconfigcheck-…" options for APKBUILDs. Generate it from the kconfigcheck.toml of the current branch, too. These options are passed from "pmbootstrap lint" to "apkbuild-lint", which we run in pmaports CI.