Github messages for voidlinux
 help / color / mirror / Atom feed
From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: harvid-0.8.3
Date: Mon, 18 Oct 2021 23:21:03 +0200	[thread overview]
Message-ID: <20211018212103.xm759mrZzQ5Qtx9ck48tR10pVnpnMd0FbBnySemGVVw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33586@inbox.vuxu.org>

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

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/pull/33586#issuecomment-946176472

Comment:
> Wouldn't it be a more elegant solution if we patch it instead of symlinking FFmpeg and FFprobe? paper suggested that, under the condition that newest FFmpeg plays nice.

Agree, would be more elegant. Either way newest FFmpeg would need to play nice since the latest "blessed" version from Ardour is 2.8.2 while Void is currently shipping 4.4.

  parent reply	other threads:[~2021-10-18 21:21 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16 10:04 [PR PATCH] " notthewave
2021-10-16 10:12 ` notthewave
2021-10-17  9:07 ` [PR PATCH] [Updated] " notthewave
2021-10-17  9:08 ` notthewave
2021-10-17  9:13 ` notthewave
2021-10-17  9:14 ` notthewave
2021-10-18 12:42 ` TinfoilSubmarine
2021-10-18 13:28 ` TinfoilSubmarine
2021-10-18 14:47 ` TinfoilSubmarine
2021-10-18 16:27 ` [PR PATCH] [Updated] " notthewave
2021-10-18 16:33 ` notthewave
2021-10-18 16:33 ` notthewave
2021-10-18 16:39 ` notthewave
2021-10-18 16:40 ` notthewave
2021-10-18 16:56 ` TinfoilSubmarine
2021-10-18 17:45 ` [PR PATCH] [Updated] " notthewave
2021-10-18 17:46 ` notthewave
2021-10-18 17:59 ` notthewave
2021-10-18 18:07 ` notthewave
2021-10-18 18:08 ` notthewave
2021-10-18 18:09 ` notthewave
2021-10-18 18:23 ` TinfoilSubmarine
2021-10-18 18:30 ` TinfoilSubmarine
2021-10-18 18:38 ` TinfoilSubmarine
2021-10-18 20:52 ` [PR PATCH] [Updated] " notthewave
2021-10-18 20:55 ` notthewave
2021-10-18 21:06 ` notthewave
2021-10-18 21:07 ` notthewave
2021-10-18 21:08 ` notthewave
2021-10-18 21:14 ` notthewave
2021-10-18 21:21 ` TinfoilSubmarine [this message]
2021-10-19  8:24 ` notthewave
2021-10-19  9:27 ` notthewave
2021-10-19  9:27 ` notthewave
2021-10-19  9:30 ` notthewave
2021-10-19  9:31 ` notthewave
2021-10-19 10:39 ` notthewave
2021-10-19 10:45 ` notthewave
2021-10-19 10:46 ` notthewave
2021-10-19 12:15 ` TinfoilSubmarine
2021-10-19 13:12 ` TinfoilSubmarine
2021-10-19 15:23 ` notthewave
2021-10-19 15:25 ` notthewave
2021-10-19 15:34 ` notthewave
2021-10-19 15:37 ` TinfoilSubmarine
2021-10-19 18:03 ` [PR PATCH] [Updated] " notthewave
2021-10-19 18:16 ` notthewave
2021-10-19 18:18 ` notthewave
2021-10-19 18:24 ` notthewave
2021-10-19 18:32 ` [PR PATCH] [Updated] " notthewave
2021-10-20  1:19 ` notthewave
2021-10-25 18:25 ` [PR REVIEW] " TinfoilSubmarine
2021-10-25 18:26 ` TinfoilSubmarine
2021-10-25 18:46 ` TinfoilSubmarine
2021-10-25 18:48 ` TinfoilSubmarine
2021-10-25 19:44 ` [PR PATCH] [Updated] " notthewave
2021-10-25 19:46 ` notthewave
2021-10-25 19:48 ` notthewave
2021-10-25 20:06 ` TinfoilSubmarine
2021-10-25 20:08 ` notthewave
2021-10-25 20:14 ` notthewave
2021-10-25 20:18 ` notthewave
2021-10-29 16:10 ` notthewave
2021-11-02 15:48 ` TinfoilSubmarine
2021-11-02 15:50 ` notthewave
2021-11-26  9:59 ` notthewave
2021-11-26 10:33 ` notthewave
2021-12-05 11:19 ` notthewave
2021-12-05 11:22 ` notthewave
2022-06-09  2:12 ` github-actions
2022-06-23  2:15 ` [PR PATCH] [Closed]: " github-actions
  -- strict thread matches above, loose matches on Subject: below --
2021-10-16  7:51 [PR PATCH] " notthewave
2021-10-16  9:05 ` notthewave
2021-10-16  9:05 ` notthewave

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=20211018212103.xm759mrZzQ5Qtx9ck48tR10pVnpnMd0FbBnySemGVVw@z \
    --to=tinfoilsubmarine@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).