Github messages for voidlinux
 help / color / mirror / Atom feed
From: lemmi <lemmi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: WIP: Update OBS to 30.0.0
Date: Mon, 23 Oct 2023 03:23:35 +0200	[thread overview]
Message-ID: <20231023012335.0eUDbOnTSHATWHkunzhBVR4d573UQrT37WVVigJ2Klc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46233@inbox.vuxu.org>

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

New comment by lemmi on void-packages repository

https://github.com/void-linux/void-packages/pull/46233#issuecomment-1774281599

Comment:
We can certainly look into adding websocket support once `30.0` has been released. 
Using `master` is [almost certainly out of the question](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements). Same goes for the browser plug-in, since that one has a [rather annoying dependency](https://github.com/obsproject/obs-studio/wiki/Build-Instructions-For-Linux#prerequisites-1) which requires packaging another browser.  

  parent reply	other threads:[~2023-10-23  1:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 23:03 [PR PATCH] " the-maldridge
2023-09-24 23:12 ` [PR PATCH] [Updated] " the-maldridge
2023-09-24 23:18 ` the-maldridge
2023-09-24 23:21 ` the-maldridge
2023-09-24 23:24 ` the-maldridge
2023-09-25  0:11 ` the-maldridge
2023-10-15  2:00 ` the-maldridge
2023-10-17 11:36 ` Lolzen
2023-10-23  0:16 ` 10leej
2023-10-23  1:23 ` lemmi [this message]
2023-10-24 12:11 ` m3tav3rse
2023-10-27 19:25 ` Lolzen
2023-11-13  7:29 ` [PR PATCH] [Updated] " the-maldridge
2023-11-13 19:40 ` the-maldridge
2023-11-13 19:44 ` [PR PATCH] [Updated] " the-maldridge
2023-11-13 19:44 ` the-maldridge
2023-11-14  1:39 ` [PR PATCH] [Merged]: " the-maldridge
2023-11-14  8:59 ` Johnnynator

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=20231023012335.0eUDbOnTSHATWHkunzhBVR4d573UQrT37WVVigJ2Klc@z \
    --to=lemmi@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).