From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] ffmpeg (5.1.2)
Date: Fri, 20 Jan 2023 14:04:04 -0700 [thread overview]
Message-ID: <67f23f7c-b355-05a1-b59d-0ba59a623689@Shaw.ca> (raw)
In-Reply-To: <5afd1512-3f5f-ab90-50b4-1e00100ea68c@dronecode.org.uk>
On 2023-01-20 11:40, Jon Turney via Cygwin-apps wrote:
> 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.
> 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?
As well as looking at:
https://src.fedoraproject.org/rpms/ffmpeg/tree/
I've found it useful to look at other work done in recent forks e.g.
https://src.fedoraproject.org/fork/yselkowitz/rpms/ffmpeg/commits/rawhide
and other distros; OpenSuSE and Arch are like Fedora; Gentoo is like Cygwin;
OpenBSD is behind on v4 so skipped:
https://github.com/bmwiedemann/openSUSE/tree/master/packages/f/ffmpeg-5
https://aur.archlinux.org/packages/ffmpeg-full
https://packages.debian.org/source/sid/ffmpeg
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-video/ffmpeg/ffmpeg-5.1.2-r1.ebuild
https://github.com/macports/macports-ports/tree/master/multimedia/ffmpeg
https://cgit.freebsd.org/ports/tree/multimedia/ffmpeg
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/multimedia/ffmpeg5/
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-01-20 21:04 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
2023-01-20 21:04 ` Brian Inglis [this message]
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=67f23f7c-b355-05a1-b59d-0ba59a623689@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-apps@cygwin.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.
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).