From: hartwork <hartwork@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libvisual: update to 0.4.2.
Date: Thu, 17 Aug 2023 14:17:59 +0200 [thread overview]
Message-ID: <20230817121759.8HHl01kcTlqdCevCCyRvCUh3bhALwFPt9RYDnGqk7_o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43912@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
New comment by hartwork on void-packages repository
https://github.com/void-linux/void-packages/pull/43912#issuecomment-1682183917
Comment:
> Hi @Piraty cool!
>
> Regarding details:
>
> * The patch applies to configure error output so if you make sure to note take the error path by (1) use of the right flags and (2) the dependencies being around and recent enough, the patch could in theory be dropped again (if you like).
>
> * Some dependencies are still missing on plugins, e.g. Alsa, portaudio, pulseaudio, glu, mesa, jack, bison (rather than flex). https://github.com/Homebrew/homebrew-core/pull/126424/files may be good to compare too, though I notice that plugins should not need SDL there either…
@Piraty any thoughts?
next prev parent reply other threads:[~2023-08-17 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 9:56 [PR PATCH] " Piraty
2023-05-17 9:58 ` [PR PATCH] [Updated] " Piraty
2023-05-17 10:02 ` Piraty
2023-08-16 1:44 ` github-actions
2023-08-17 12:17 ` hartwork [this message]
2023-08-18 23:05 ` [PR PATCH] [Updated] " Piraty
2023-08-18 23:24 ` Piraty
2023-08-18 23:24 ` Piraty
2023-11-17 1:46 ` github-actions
2023-11-17 13:33 ` hartwork
2023-11-19 9:15 ` [PR PATCH] [Updated] " Piraty
2023-11-19 9:17 ` Piraty
2023-11-20 23:39 ` [PR PATCH] [Merged]: " Piraty
2023-11-21 0:43 ` hartwork
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=20230817121759.8HHl01kcTlqdCevCCyRvCUh3bhALwFPt9RYDnGqk7_o@z \
--to=hartwork@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).