Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: gamescope-3.14.1
Date: Fri, 16 Feb 2024 02:36:01 +0100	[thread overview]
Message-ID: <20240216013601.2BE0824B51@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48354@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

There's a merged pull request on the void-packages repository

New package: gamescope-3.14.1
https://github.com/void-linux/void-packages/pull/48354

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
Add Valve's Gamescope as requested in #36869. If this is merged, `steamos-compositor` should probably be removed from the repository at some point.

This PR also adds `libliftoff` as a dependency. Gamescope also vendors some dependencies, but I believe I've handled this correctly.

#### 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.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)


      parent reply	other threads:[~2024-02-16  1:36 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 16:45 [PR PATCH] New package: gamescope-3.14.0 dexgs
2024-01-24 17:34 ` [PR PATCH] [Updated] " dexgs
2024-01-24 23:09 ` dexgs
2024-01-24 23:13 ` dexgs
2024-01-24 23:32 ` dexgs
2024-01-24 23:37 ` dexgs
2024-01-24 23:51 ` dexgs
2024-01-31  2:37 ` [PR REVIEW] " classabbyamp
2024-01-31  2:37 ` classabbyamp
2024-01-31  2:37 ` classabbyamp
2024-01-31  2:37 ` classabbyamp
2024-01-31  2:37 ` classabbyamp
2024-01-31  2:37 ` classabbyamp
2024-01-31 14:35 ` [PR PATCH] [Updated] " dexgs
2024-01-31 14:36 ` dexgs
2024-01-31 14:38 ` dexgs
2024-01-31 16:17 ` [PR REVIEW] " classabbyamp
2024-01-31 16:17 ` classabbyamp
2024-01-31 16:17 ` classabbyamp
2024-01-31 16:17 ` classabbyamp
2024-01-31 16:40 ` [PR PATCH] [Updated] " dexgs
2024-01-31 16:42 ` dexgs
2024-02-01  0:17 ` classabbyamp
2024-02-01  0:19 ` [PR PATCH] [Updated] " dexgs
2024-02-01  0:19 ` dexgs
2024-02-01  0:33 ` classabbyamp
2024-02-01  2:08 ` dexgs
2024-02-01  2:09 ` dexgs
2024-02-02 14:08 ` [PR PATCH] [Updated] " dexgs
2024-02-02 14:09 ` dexgs
2024-02-11 16:26 ` [PR PATCH] [Updated] " dexgs
2024-02-15  6:15 ` [PR REVIEW] " classabbyamp
2024-02-15  6:15 ` classabbyamp
2024-02-15  6:16 ` classabbyamp
2024-02-16  0:42 ` [PR PATCH] [Updated] " dexgs
2024-02-16  0:44 ` dexgs
2024-02-16  0:46 ` [PR PATCH] [Updated] " dexgs
2024-02-16  0:51 ` New package: gamescope-3.14.1 classabbyamp
2024-02-16  1:02 ` classabbyamp
2024-02-16  1:04 ` classabbyamp
2024-02-16  1:10 ` [PR PATCH] [Updated] " dexgs
2024-02-16  1:11 ` dexgs
2024-02-16  1:11 ` dexgs
2024-02-16  1:36 ` classabbyamp [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=20240216013601.2BE0824B51@inbox.vuxu.org \
    --to=classabbyamp@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).