New comment by ram02z on void-packages repository

https://github.com/void-linux/void-packages/pull/33578#issuecomment-1187566090

Comment:
> I'm not sure to what extend `wofi` fills the need for `rofi` on Wayland, but I don't think this is a good candidate for a separate package. It uses the same name and shadows upstream versions, leading to confusion about the authoritative upstream. The `replaces` directive here (incorrectly used) masks a conflict caused by executable naming that deepens confusion about what is running from where.
> 
> The original `rofi` author, still actively developing the software, has shown no interest in Wayland support. If this work won't be upstreamed, it's probably time for the fork maintainer to take the project in its own direction. We could talk about the value of moving the main package to a fork that provides both X and Wayland support, but given that the original project is still actively developed, that's going to be a tough sale.

That's fair, but I did ask if the `replaces` directive was correct here but didn't get a response.

As far as I know, wofi is unmaintained but it worked fine when I tried it.

For anyone still interested in using the rofi-wayland fork, I have it in my public repository; github.com/ram02z/void-templates