From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: ncdehnel@gmail.com, 43418@debbugs.gnu.org, leo@famulari.name
Subject: bug#43418: ffprobe/avprobe and ffmpeg/avconv should be added as dependencies of youtube-dl so it will function correctly
Date: Wed, 16 Sep 2020 10:58:14 +0200 [thread overview]
Message-ID: <875z8ertcp.fsf@nckx> (raw)
In-Reply-To: <87mu1q9lyw.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
Leo, Mark,
Mark H Weaver 写道:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Tue, Sep 15, 2020 at 02:06:11PM +0200, Tobias Geerinckx-Rice
>> via Bug reports for GNU Guix wrote:
>>> Matters would be different if the error message were less
>>> clear, or perhaps
>>> if ffmpeg weren't so insanely great:
>>>
>>> λ guix size youtube-dl | tail -n1
>>> total: 186.9 MiB
>>> λ guix size youtube-dl ffmpeg | tail -n1
>>> total: 811.2 MiB
>>
>> I wonder, should we expect FFmpeg to already be referenced by
>> somebody's
>> profile if they are using youtube-dl? VLC and mpv both depend
>> on FFmpeg.
>> The use case of "download video and watch it on another machine
>> (or
>> never watch it)" seems somewhat esoteric.
I don't see why my use case should be sidelined as ‘esoteric’.
;-)
> However, in my recent experience, youtube usually provides the
> freedom-respecting formats only as separate audio and video
> streams
> which must be recombined by youtube-dl, and in that case the
> 'ffmpeg'
> command line tool seems to be required.
This is a good argument. If including ffmpeg by default makes it
easier to request & mux freeër formats, let's do that.
> I see two possible approaches: ffmpeg could be added to
> youtube-dl's
> propagated-inputs, or it could be instead be added to 'inputs',
> and we
> could substitute hardcoded paths to 'ffmpeg' in the built
> 'youtube-dl'.
> I generally tend to favor the latter approach, but there are
> valid
> arguments for each approach and I don't feel strongly about it.
Which advantages does the former have? I wasn't aware of any.
Thanks!
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-09-16 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 11:27 bug#43418: ffprobe/avprobe and ffmpeg/avconv should be added as dependencies of youtube-dl so it will function correctly Nathan Dehnel
2020-09-15 12:06 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-09-15 19:34 ` raingloom
2020-09-15 23:52 ` Nathan Dehnel
2020-09-15 23:17 ` Leo Famulari
2020-09-16 8:14 ` Mark H Weaver
2020-09-16 8:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-09-16 11:30 ` Mark H Weaver
2020-09-16 9:54 ` bug#43418: [PATCH] gnu: youtube-dl: Refer to ffmpeg Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-09-16 11:31 ` Mark H Weaver
2020-09-16 11:54 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-09-16 12:07 ` zimoun
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=875z8ertcp.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=43418@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
--cc=mhw@netris.org \
--cc=ncdehnel@gmail.com \
/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).