From: brunothedev <brunothedev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Packaging dependencies for wayland in qtile
Date: Fri, 23 Dec 2022 21:01:35 +0100 [thread overview]
Message-ID: <20221223200135.a5MOC0zTRIKf9Dp_-HRAGRddoGoWl8_4nLa5c6WFCAc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40837@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
There's a closed pull request on the void-packages repository
Packaging dependencies for wayland in qtile
https://github.com/void-linux/void-packages/pull/40837
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
# Introduction
Before getting into the pull request, i would like to tell that this is my first contribution to void-linux/void-packages, so i am sorry if i made any mistakes(I probably added too much dependencies), i would also like to point out that this pull request may be needed to be splitted, since it adds 3 packages and modify 1 package.
## Summary
This pull request add the following packages:
- python-pywayland
- python-xkbcommon
- pywlroots
This pull request modify:
- qtile
## Reason
The reason i made this pull request is to add all the dependencies to use qtile with the wayland backend
prev parent reply other threads:[~2022-12-23 20:01 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 16:51 [PR PATCH] " brunothedev
2022-11-29 16:58 ` [PR REVIEW] " classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 17:02 ` brunothedev
2022-11-29 18:10 ` ahesford
2022-11-29 18:19 ` [PR PATCH] [Updated] " brunothedev
2022-11-29 18:21 ` [PR REVIEW] " brunothedev
2022-11-29 18:35 ` ahesford
2022-11-29 18:56 ` [PR PATCH] [Updated] " brunothedev
2022-11-29 19:28 ` brunothedev
2022-11-29 20:02 ` brunothedev
2022-11-29 23:22 ` paper42
2022-11-29 23:26 ` [PR REVIEW] " paper42
2022-11-29 23:26 ` paper42
2022-11-29 23:26 ` paper42
2022-11-30 0:43 ` brunothedev
2022-11-30 0:43 ` [PR PATCH] [Closed]: " brunothedev
2022-11-30 0:43 ` brunothedev
2022-11-30 0:45 ` paper42
2022-11-30 0:54 ` brunothedev
2022-11-30 1:13 ` [PR PATCH] [Updated] " brunothedev
2022-11-30 9:47 ` [PR REVIEW] " sgn
2022-11-30 12:37 ` [PR PATCH] [Updated] " brunothedev
2022-11-30 13:29 ` ahesford
2022-11-30 14:18 ` [PR PATCH] [Updated] " brunothedev
2022-12-05 18:51 ` brunothedev
2022-12-05 18:53 ` classabbyamp
2022-12-06 12:51 ` brunothedev
2022-12-23 20:01 ` brunothedev
2022-12-23 20:01 ` brunothedev [this message]
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=20221223200135.a5MOC0zTRIKf9Dp_-HRAGRddoGoWl8_4nLa5c6WFCAc@z \
--to=brunothedev@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).