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

Thanks again for working on this package!

On Sat, Jan 28, 2023 at 01:33:44PM +0100, Tobias Geerinckx-Rice via Guix-patches via wrote:
> > I've also moved ffmpeg form inputs to propagated-inputs
> 
> Please avoid propagation whenever possible; it breaks all kinds of nice
> things.

I'm here to express my weak preference for dynamically binding FFmpeg in
use cases like this one.

That means, I prefer if packages like svtplay-dl do not depend on FFmpeg
at all, but rather expect the user to install FFmpeg alongside them.

I prefer this because I use a custom FFmpeg professionally as a video
engineer, and it's easier to use it with Guix packages if the dependency
is resolved at run-time rather than at build-time.

I'd expect that many people like me also use a variety of custom FFmpeg
builds for different use cases.

Like I said, it's a weak preference. And I probably wouldn't use
svtplay-dl at work in the US, although I do use youtube-dl / yt-dlp. Let
me know what you think.




  parent reply	other threads:[~2023-03-05 20:14 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 [this message]
2023-03-05 20:15     ` Jessica Tallon
2023-03-05 20:58       ` Leo Famulari

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=ZAT38GWzsqoHVXHk@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).