Commits on Source (26)
-
Caleb Connolly authored
We plan to ship systemd with split /usr until the /usr merge is complete in Alpine. Let's not drop all our code yet but just forcefully disable it. Signed-off-by:
Caleb Connolly <caleb@postmarketos.org>
-
Fixes #2456 Depends on https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/72741
-
-
Oliver Smith authored
For packages selected by the user (see last commit), set the provider_priority to 999999 instead of 999. The previous number seems not high enough, we might set this in the APKBUILDs.
-
Oliver Smith authored
-
Oliver Smith authored
The previous version would fail if the suffix contained a dash as well, e.g. postmarketos-base-ui-audio-some-new-thing. Fix it and add example comments.
-
This is probably a leftover from automatically reformatting this file.
-
-
This is section is not meant to represent my opinions, rather I seek to document the status quo. I base the support range on what's been reasoned in prior merge requests such as [1] and [2], as well as [3] which only fixed CI in the one active stable release and left old stable releases unfixed. While I don't necessary think this is a great situation given that old releases may sometimes be useful, extending the time pmbootstrap has to support old releases would incur significant additional maintenance effort and consequently require more discussion than just documenting what's already happening. As such, I think this is the most reasonable thing to do for now. [1]: https://gitlab.com/postmarketOS/pmbootstrap/-/merge_requests/2360#note_1999012908 [2]: https://gitlab.com/postmarketOS/pmbootstrap/-/merge_requests/2417#note_2135527528 [3]: https://gitlab.com/postmarketOS/pmaports/-/merge_requests/5676
-
Newbyte authored
We moved from gitlab.com to gitlab.postmarketos.org.
-
Newbyte authored
-
Otherwise Arch may be None here which results in an error.
-
Now that we don't need weird apk-tools hacks for systemd, we can re-implement this optimisation and always run apk static rather than running apk through the chroot. Signed-off-by:
Caleb Connolly <caleb@postmarketos.org>
-
-
This could be re-purposed in the future in case we migrate URLs again. Co-authored-by:
Caleb Connolly <caleb@postmarketos.org> Tweaked-by:
Oliver Smith <ollieparanoid@postmarketos.org>
-
Oliver Smith authored
When running some commands like "pmbootstrap chroot" or even "pmbootstrap work_migrate", pmbootstrap will attempt to read the pmaports.cfg from origin/master *before* doing the work dir migration. In order to do this, the "get_upstream_remote" function tries to find the upstream remote by URL. Let it search with the outdated URLs too, so this doesn't fail right before migrating to the new URLs.
-
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.
-
-
-
-
-
Showing
- README.md 16 additions, 0 deletionsREADME.md
- pmb/aportgen/__init__.py 11 additions, 4 deletionspmb/aportgen/__init__.py
- pmb/aportgen/busybox_static.py 2 additions, 1 deletionpmb/aportgen/busybox_static.py
- pmb/aportgen/core.py 15 additions, 16 deletionspmb/aportgen/core.py
- pmb/aportgen/gcc.py 3 additions, 2 deletionspmb/aportgen/gcc.py
- pmb/aportgen/grub_efi.py 1 addition, 1 deletionpmb/aportgen/grub_efi.py
- pmb/aportgen/musl.py 3 additions, 2 deletionspmb/aportgen/musl.py
- pmb/build/_package.py 7 additions, 6 deletionspmb/build/_package.py
- pmb/build/newapkbuild.py 5 additions, 5 deletionspmb/build/newapkbuild.py
- pmb/chroot/apk.py 2 additions, 2 deletionspmb/chroot/apk.py
- pmb/chroot/apk_static.py 3 additions, 3 deletionspmb/chroot/apk_static.py
- pmb/chroot/init.py 5 additions, 0 deletionspmb/chroot/init.py
- pmb/commands/__init__.py 6 additions, 1 deletionpmb/commands/__init__.py
- pmb/commands/aportgen.py 21 additions, 0 deletionspmb/commands/aportgen.py
- pmb/commands/pkgver_bump.py 20 additions, 0 deletionspmb/commands/pkgver_bump.py
- pmb/commands/pull.py 2 additions, 2 deletionspmb/commands/pull.py
- pmb/config/__init__.py 9 additions, 11 deletionspmb/config/__init__.py
- pmb/config/init.py 1 addition, 1 deletionpmb/config/init.py
- pmb/core/dps.py 131 additions, 0 deletionspmb/core/dps.py
- pmb/helpers/apk.py 13 additions, 34 deletionspmb/helpers/apk.py
pmb/commands/aportgen.py
0 → 100644
pmb/commands/pkgver_bump.py
0 → 100644
pmb/core/dps.py
0 → 100644