From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: rofi-wayland-1.7.3
Date: Mon, 18 Jul 2022 16:15:51 +0200 [thread overview]
Message-ID: <20220718141551.03t-B25sZpEpigREEKWPq7KPvHpE9XwWC6Nbnm9f44E@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: 1830 bytes --]
There's a closed pull request on the void-packages repository
New package: rofi-wayland-1.7.3
https://github.com/void-linux/void-packages/pull/33578
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
Inspired by the alpine package, I have disabled xcb to make it wayland only. See https://github.com/lbonn/rofi/pull/31
An alternative would be to switch the current rofi template to use this fork to allow for wayland support.
I have attempted to keep the dependencies to a minimum, so I would appreciate if anyone testing this can let me know if there are missing dependencies.
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
next prev parent reply other threads:[~2022-07-18 14:15 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 ` ahesford [this message]
2022-07-18 14:25 ` ram02z
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=20220718141551.03t-B25sZpEpigREEKWPq7KPvHpE9XwWC6Nbnm9f44E@z \
--to=ahesford@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).