Thank you, dataaja95! I just checked, espeakup is in Alpine's testing repository. This means it can be installed in Alpine edge / postmarketOS edge.

I've verified that it works as expected now on v24.06 :) This can be closed, thanks!

Perfect, thank you very much!

Ah indeed sxmo_hook_wallpaper.sh isn't in Sxmo 1.5.2 yet. But this is a really elegant solution, looking forward to using this :)

I think we "just" have to tag a release, and add the dependency in the pmaports sxmo recipes. As usual, we are not in time for the pmos releases :')

Regarding v24.06 release timeline: today was the feature freeze, and tomorrow the testing week starts. After that comes the release week: https://wiki.postmarketos.org/wiki/Creating_a_release_branch#Timeline

It would of course be great to have the next Sxmo version in v24.06, and we could make an exception for it from the feature freeze, if you think it is ready. Is that the case, and could you tag a release today or early in the coming week? (The earlier it is tagged, the more time is for testing.)

Alternatively I would propose to backport the wallpaper patch to 1.5.2.

What do you think?

Ah I just realized, there already was a patch: https://lists.sr.ht/~mil/sxmo-devel/patches/49309

Thanks, Willow!

I guess I'll need to set $SXMO_OS for this... will look more into this soon.

Hey SXMO folks,

as the v24.06 release of pmOS is around the corner, I'm finally finishing up things from this discussion in IRC from January:

ollieparanoid: I have a question for SXMO maintainers: how would you feel about having the default wallpaper for Sxmo changed in postmarketOS? ollieparanoid: a great wallpaper artist dikasp showed up and made some amazing ones here: https://gitlab.com/postmarketOS/artwork/-/merge_requests/25 ollieparanoid: so we could actually have one per postmarketOS release. they made it for GNOME initially, but we are already considering using it for other UIs too like Plasma Mobile, and possibly Sxmo. anjan: I will ask about those wallpapers. They really do look beautiful :D staceee: seems great! we would have to refactor a bit how we select the picture, but should be easy for us

The wallpaper is already set for GNOME, Phosh and (MR open) Plasma Mobile.

So how would I set it for Sxmo? I've browsed a bit through the source, and I guess an elegant way could be writing a /etc/profile.d/sxmo_set_pmos_wallpaper.sh, which contains:

export SXMO_BG_IMG="/usr/share/wallpapers/postmarketos.jpg"

However this doesn't work currently. I guess the script that gets installed to ~/.config/sxmo/profile would need to be changed to not set SXMO_BG_IMG, if it was already set by an environment variable before.

Does it make sense to do it like this, or do you have a better suggestion?

If you have time, could you adjust the mentioned profile script so this works? We could then backport this patch to sxmo-utils in alpine edge and 3.20, so it ends up in pmOS v24.06.

More details on packaging: /etc/profile.d/sxmo_set_pmos_wallpaper.sh will live in a new postmarketos-artwork-wallpapers-sxmo subpackage, which has install_if for sxmo and postmarketos-artwork-wallpapers. Then postmarketos-artwork-wallpapers will be added to _pmb_recommends of Sxmo UIs. That way people could just uninstall the package if they prefer to have the default wallpaper.

Thank you very much!

It would be great to have proper screen reader support out of the box in one of the UIs on linux mobile and Sxmo seems like a great candidate for it. The demo with numen also looks impressive: https://lists.sr.ht/~mil/sxmo-devel/%3C20221108215538.rhg6ja4m6nfv62s3%40trantor%3E

An issue in the postmarketOS tracker was recently created showing interest in accessibility features, so if somebody is interested in implementing this or discussing ideas, consider reaching out there: https://gitlab.com/postmarketOS/pmaports/-/issues/2321

Regarding the keeping-it-lightweight aspect, maybe the screenreader feature could be implemented optionally (and for pmOS users would chose whether to enable it or not during the installer in the future?)

I've added this issue to: https://wiki.postmarketos.org/wiki/Accessibility#Related_issues

I think a script that parses pkgs.postmarketos.org and checks against edge pkgs.alpinelinux.org is best. I cant find an api for pkgs.postmarketos.org. If you guys have a better way to program this or make it easier for you to support, let me know.

I suggest looking in the pmaports.git / aports.git repositories directly, instead of the pkgs websites. The latter gets generated from the git repositories, after binary packages are built and are sent to the backends that parse them and put the information into a database for these websites. By parsing the git repositories directly, it is more accurate (no delay until packages are built), and you should also be able to checkout a merge request for the service pack and review what packages are in there vs. alpine edge.

I got this after upgrading from 1.5.x to 1.6.0. Apparently this is known:

https://gitlab.com/postmarketOS/pmaports/-/merge_requests/2684#note_735418873

It was gone after another reboot.

Fixed here: https://gitlab.com/postmarketOS/pmaports/-/merge_requests/2631

Edge blog post: https://postmarketos.org/edge/2021/10/24/sway-swmo/