

As far as I understand it, it’s more of a push to wayland by default and not about harming x11 users. I for one would like to avoid having kwin-x11 pushed to my system.
Linux enthusiast, family man and nerd
As far as I understand it, it’s more of a push to wayland by default and not about harming x11 users. I for one would like to avoid having kwin-x11 pushed to my system.
So Alpaca still gives functional answers if you turn off your internet connection?
In the end the creator of the game kindly send me links to AUR packages that other people had done for his other projects so I could see what they had done and I did and did the same, which was to put the files in the locations recommended by the specs like /etc and /usr, and to added a post-install message telling the user to copy/paste some commands to copy the files in $HOME. It’s a bit clunky but I guess it works 🥳
Curious, if it was the tui-mines and tui-sudoku packages you took inspiration from? If that’s the case, then those are packages I maintain.
I chose to do some AUR packages, because I wanted to learn how to package for Arch, packaging guidelines and get a routine going.
I believe the reason to not mess with $HOME in packaging, is because of security. $HOME is the users private stash. To put stuff in there, from packaging, means you invade their private space and users should be able to decide what they want “dumped” in there. So just installing a package, should not put stuff in a users home folder.
AUR package maintainers are not the same as Arch repo package maintainers. Anyone can be an AUR package maintainer.
Because no Package Maintainer wants to maintain it, is my guess.
There is, but it is not great at handling conflicts, and other yes/no questions pacman might ask. This can lead to something going wrong during installation or updates.
Plasma/KDE decided it should be the default a long time ago and the X11 session has been in maintenance mode ever since.