unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Jessica Tallon <tsyesika@tsyesika.se>
Cc: 61117@debbugs.gnu.org
Subject: [bug#61117] Update svtplay-dl to 4.18
Date: Sun, 5 Mar 2023 15:58:27 -0500	[thread overview]
Message-ID: <ZAUCc9BV6djyf4Fp@jasmine.lan> (raw)
In-Reply-To: <87sfej3pj1.fsf@tsyesika.se>

On Sun, Mar 05, 2023 at 09:15:14PM +0100, Jessica Tallon wrote:
> I think I have a mild opinion for having it bring in ffmpeg, this is
> mostly for three reasons:
> 
> - There isn't a good way to communicate to users that they might wish to
>   pull in ffmpeg.
>   
> - svtplay-dl will download both audio and video parts and then realise
>   it doesn't have ffmpeg and will give up producing a warning. This
>   leaves it up to the user to fix, while a merging both files is a
>   simple job it often has me searching through a manual as I'm not well
>   versed in ffmpeg or similar.
> 
> - I like it when things work consistantly (if x version of svtplay-dl
>   works a specific way on my machine, it should on another machine, not
>   dependent on my profile)
> 
> My preference is mild though, let me know what you think!

I think you should go with your method!




      reply	other threads:[~2023-03-05 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 11:29 [bug#61117] Update svtplay-dl to 4.18 Jessica Tallon
2023-01-28 12:33 ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-28 12:58   ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-28 13:02   ` Tobias Geerinckx-Rice via Guix-patches via
2023-03-05 10:05   ` Jessica Tallon
2023-03-05 10:39   ` Jessica Tallon
2023-03-05 20:13   ` Leo Famulari
2023-03-05 20:15     ` Jessica Tallon
2023-03-05 20:58       ` Leo Famulari [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZAUCc9BV6djyf4Fp@jasmine.lan \
    --to=leo@famulari.name \
    --cc=61117@debbugs.gnu.org \
    --cc=tsyesika@tsyesika.se \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).