WIP: Package the touch keyboard onboard and polybar (for i3)
Compare changes
Files
6
aports/main/onboard/APKBUILD
0 → 100644
+ 28
− 0
This adds the software required to replicate the i3touchmenu setup that makes i3 quite usable on a tablet without a keyboard. With some modifications this might also be usable on a phone. The fonts are partially missing, unfortunately, so just copying the setup does not work. More specifically, I have packaged:
py3-distutils-extra
and py3-dbus
as new packages.Some questions:
onboard
uses the error()
method of glibc. From the manual I understood that the way it is used (errnum=0
), this would only add the program name as prefix and then just print the rest similar to printf
. Therefore, I have replaced them with fprintf
to stderr
which is not equivalent but at least shows the messages. Is there a better fix?onboard
does not require py3-dbus
, but without py3-dbus
, some functionality is missing like showing the keyboard instead of starting a second instance when running onboard
again. As I think this is quite difficult to discover, I have just added py3-dbus
as a dependency.py3-dbus
shares some files with py-dbus
, that's why Arch Linux has a third package with the common files (see PKGBUILD). How is such a situation handled in Alpine Linux?polybar
are actually optional (only required for certain modules) but the build system just added them as dependencies. As mentioned in the discussion in the AUR, if the packages are not present during the build, they also cannot be enabled later, that's why I have added them as build dependencies. Should they be added as regular dependencies in the APKBUILD
?polybar
has two git submodules, therefore a regular git archive does not work. I am now just using git directly. There are several alternatives though. Alpine Linux has an example how to create an archive manually (but I assume this does only work for packages built in their systems). One could also just download the archives of the submodules manually. Any opinions?