From: Jon Turney <jon.turney@dronecode.org.uk>
To: takashi Yano <takashi.yano@nifty.ne.jp>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] ffmpeg (5.1.2)
Date: Fri, 20 Jan 2023 18:40:44 +0000 [thread overview]
Message-ID: <5afd1512-3f5f-ab90-50b4-1e00100ea68c@dronecode.org.uk> (raw)
In-Reply-To: <20230120193540.a32d7180d8fa690f886ef625@nifty.ne.jp>
On 20/01/2023 10:35, Takashi Yano via Cygwin-apps wrote:
> I would like to propose new package ffmpeg which is
> well known audio/video tool. ffmpeg is ported to
> many linux distributions and other unix like systems
> as well as widows. Since there is windows build,
> the demand of cygwin port might be relatively small,
> however its libraries are usefull for other softwares.
>
> I have posted another ITP for MOC (Music On Console)
> which is a ncurses based music player, whose plugin
> uses ffmpeg libraries.
>
> I have already prepared the ffmpeg package as follows.
>
> https://tyan0.yr32.net/cygwin/x86_64/release/ffmpeg/
>
> To build ffmpeg, other new packages i.e., x264, x265 and
> xvidcore are required, I have proposed ITP at the same
> time.
Thanks!
For a long time, ffmpeg was not included in Fedora, due to concerns
about codec patents, but those issues seem to have been resolved.
Can you please investigate what configuration is used in Fedora, and
what the effects of matching that would be?
next prev parent reply other threads:[~2023-01-20 18:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 10:35 Takashi Yano
2023-01-20 15:04 ` Thomas Wolff
2023-01-20 15:28 ` Takashi Yano
2023-01-20 15:47 ` Thomas Wolff
2023-01-20 15:58 ` Takashi Yano
2023-01-20 20:05 ` Thomas Wolff
2023-01-22 12:20 ` Takashi Yano
2023-01-20 18:40 ` Jon Turney [this message]
2023-01-20 21:04 ` Brian Inglis
2023-01-22 12:25 ` Takashi Yano
2023-01-24 3:28 ` Takashi Yano
2023-02-04 16:45 ` Jon Turney
2023-02-05 8:40 ` Takashi Yano
2023-02-06 13:53 ` Takashi Yano
2023-02-13 18:28 ` Jon Turney
2023-02-14 9:11 ` Takashi Yano
2023-02-16 18:48 ` Jon Turney
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=5afd1512-3f5f-ab90-50b4-1e00100ea68c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).