From: ram02z <ram02z@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: rofi-wayland-1.7.3
Date: Mon, 18 Jul 2022 16:25:05 +0200 [thread overview]
Message-ID: <20220718142505.rLpWw1HRYS13kWsRi6aZ5WOt355f1ll1lOZm5qOrlDY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33578@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
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
next prev parent reply other threads:[~2022-07-18 14:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 19:46 [PR PATCH] New package: rofi-wayland-1.7.0 ram02z
2021-10-15 19:54 ` [PR PATCH] [Updated] " ram02z
2021-10-15 19:59 ` ram02z
2021-10-15 20:08 ` ram02z
2021-10-15 22:34 ` ram02z
2021-10-15 22:40 ` ram02z
2021-10-17 10:41 ` ram02z
2021-10-17 10:42 ` ram02z
2021-10-17 11:20 ` ram02z
2021-10-17 11:20 ` [PR PATCH] [Updated] " ram02z
2021-11-03 18:58 ` [PR REVIEW] " TinfoilSubmarine
2021-11-03 19:01 ` ram02z
2021-11-03 19:14 ` TinfoilSubmarine
2021-12-21 23:21 ` [PR PATCH] [Updated] " ram02z
2021-12-22 13:21 ` [PR PATCH] [Updated] New package: rofi-wayland-1.7.2 ram02z
2021-12-22 14:37 ` ram02z
2022-01-30 23:12 ` ram02z
2022-02-01 23:44 ` [PR PATCH] [Updated] New package: rofi-wayland-1.7.3 ram02z
2022-03-03 15:14 ` ram02z
2022-06-08 2:12 ` github-actions
2022-06-08 7:51 ` ram02z
2022-07-18 14:15 ` ahesford
2022-07-18 14:15 ` [PR PATCH] [Closed]: " ahesford
2022-07-18 14:25 ` ram02z [this message]
2022-07-18 14:35 ` paper42
2022-07-18 14:50 ` ram02z
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220718142505.rLpWw1HRYS13kWsRi6aZ5WOt355f1ll1lOZm5qOrlDY@z \
--to=ram02z@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).