I've joined the list at Dan's suggestion, as I will be maintaining
waypipe now, and admittedly it could be useful for sway users, so why
Looking at the SIG page there is a wishlist item for "redshift with
wayland support", and as a big user myself I would be all for it.
The problem is that upstream has not been very active for a while -
merged one PR in 2019, but that aside pretty much nothing since 2018.
Frankly major DEs (gnome, KDE) incorporate the feature natively so users
of redshift on wayland will basically only ever be wlroots-based
compositors, so we shouldn't expect to get much help from anywhere on
this... I imagine the dev uses gnome as he wrote the gnome-clock
location helper redshift-gtk service files, so he's made the switch and
hasn't looked back much.
The wayland support issue suggests arch uses minus7's wayland
branch but that would appear to still be AUR and they are in the same
situation as us (some coprs have it alongside older versions of sway but
I would suggest the way forward would be to try to discuss with jonls
and minus7 if an official fork could start somewhere; either minus7 tree
if he is willing to do it or I suppose I could (I also have vested
interest, I am also using the stdin remote control patches discussed on
this issue, so "just" wayland wouldn't be enough for me, and whoever
takes over would need to be willing to deal with at least accepting PRs
So, what do you folks think? Worth a shot?
I'm wondering if we should re-assign the primary maintainer for sway? It
seems like some of you are a lot more active in the sway ecosystem than
If anyone is interested, please let me know!