This website requires JavaScript.
Explore
Help
Sign In
forge
/
pmaports
Watch
1
Star
0
Fork
You've already forked pmaports
0
Code
Issues
2
Pull requests
Projects
Releases
Packages
Wiki
Activity
Actions
f9c33329da
pmaports
/
main
/
postmarketos-base
/
postmarketos-base.post-install
7 lines
83 B
Text
Raw
Normal View
History
Unescape
Escape
main/postmarketos-base: fix wpa_supplicant config (!365) Fix wifi on htc-ace by properly setting nl80211 before wext. /etc/conf.d/wpa_supplicant is supposed to get modified twice with the current code in the post-install file. The first one was patched recently to set nl80211 before wext, but that change does not work in practice, for two reasons: 1. The code block does not even get executed, because apk reports that /etc/conf.d/wpa_supplicant was already modified (by a package that was installed before, in its post-install script? I could not find out which one does that though). 2. Even if it worked, the second code block would revert the change and put wext before nl80211 again. Fix this by removing the first code block, and changing the order in the second one. Make it easier to catch such errors in the future, by printing, which files get modified, or get skipped. Set "#!/bin/sh -e", so the script can not fail silently. When doing pmbootstrap -y zap and then pmbootstrap install, the output looks like this: (141/151) Installing postmarketos-base (3-r26) Executing postmarketos-base-3-r26.post-install - Modifying: /etc/fstab - Modifying: /etc/issue - Modifying: /etc/motd - Modifying: /etc/conf.d/syslog - Modifying: /etc/conf.d/wpa_supplicant - Modifying: /etc/sudoers - Modifying: /etc/chrony/chrony.conf
2019-05-14 19:00:15 +00:00
#!/bin/sh -e
Put postmarketOS aports inside pmbootstrap repo Later, the aports folder will probably get split up in its own repository. But right now this is simply convenient.
2017-05-26 20:26:25 +00:00
main/postmarketos-base: make apk interactive by default (MR 3444) This would mitigate issues where apk unexpectedly replaces packages somewhat as this way the user will be able to see precisely what changes will happen to their system before they are committed. Furthermore, most users are likely accustomed to package managers like apt, dnf, pacman, among others that all are interactive by default and as such this would provide a more familiar experience for them. This will not affected pre-existing installs, and advanced users who do not like this behaviour can restore the old one by deleting /etc/apk/interactive. [ci:skip-build]: already built successfully in CI
2022-09-16 09:59:11 +00:00
# Make apk interactive by default
touch /etc/apk/interactive
*/*: add missing exit 0 in post-install scripts (MR 1166)
2020-05-10 16:08:33 +00:00
exit 0
Reference in a new issue
Copy permalink