From: Leo Famulari <leo@famulari.name>
To: Brice Waegeneire <brice@waegenei.re>
Cc: 40060@debbugs.gnu.org
Subject: [bug#40060] [PATCH 1/2] gnu: youtube-dl: Use ffmpeg and pycryptodome
Date: Sat, 14 Mar 2020 13:21:14 -0400 [thread overview]
Message-ID: <20200314172114.GA23019@jasmine.lan> (raw)
In-Reply-To: <20200314144221.17112-1-brice@waegenei.re>
On Sat, Mar 14, 2020 at 03:42:20PM +0100, Brice Waegeneire wrote:
> * gnu/packages/video.scm (youtube-dl)[arguments]: Add phase
> wrap-executable.
> [inputs]: Add ffmpeg.
> [propagated-inputs]: Add python-pycryptodome.
What do these added dependencies do?
next prev parent reply other threads:[~2020-03-14 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 14:34 [bug#40060] [PATCH 0/2] youtube-dl add ffmpeg, pycryptodome and zsh-completion Brice Waegeneire
2020-03-14 14:42 ` [bug#40060] [PATCH 1/2] gnu: youtube-dl: Use ffmpeg and pycryptodome Brice Waegeneire
2020-03-14 17:21 ` Leo Famulari [this message]
2020-03-14 17:39 ` Brice Waegeneire
2020-03-14 17:47 ` Leo Famulari
2020-03-14 22:20 ` Tobias Geerinckx-Rice via Guix-patches via
2020-03-14 22:17 ` Tobias Geerinckx-Rice via Guix-patches via
2020-03-15 17:25 ` Leo Famulari
2020-03-17 9:06 ` Brice Waegeneire
2020-03-14 14:42 ` [bug#40060] [PATCH 2/2] gnu: youtube-dl: Add zsh completion Brice Waegeneire
2020-03-23 17:15 ` [bug#40060] [PATCH v2 0/2] youtube-dl add ffmpeg and zsh-completion Brice Waegeneire
2020-03-23 17:15 ` [bug#40060] [PATCH v2 1/2] gnu: youtube-dl: Add 'ffmpeg' as input Brice Waegeneire
2020-03-23 17:15 ` [bug#40060] [PATCH v2 2/2] gnu: youtube-dl: Add zsh completion Brice Waegeneire
2020-03-23 19:28 ` [bug#40060] [PATCH v2 0/2] youtube-dl add ffmpeg and zsh-completion Mathieu Othacehe
2020-03-23 20:23 ` Brice Waegeneire
2020-03-23 20:43 ` Mathieu Othacehe
2020-04-01 13:01 ` [bug#40060] [PATCH v3] gnu: youtube-dl: Add 'ffmpeg' as input Brice Waegeneire
2020-04-01 13:40 ` Tobias Geerinckx-Rice via Guix-patches via
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=20200314172114.GA23019@jasmine.lan \
--to=leo@famulari.name \
--cc=40060@debbugs.gnu.org \
--cc=brice@waegenei.re \
/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).