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: Sat, 4 Feb 2023 16:45:13 +0000 [thread overview]
Message-ID: <e99baaf9-21a5-ed5c-046d-535a17dd80e9@dronecode.org.uk> (raw)
In-Reply-To: <20230124122850.acbc1fb3135d376122783d05@nifty.ne.jp>
On 24/01/2023 03:28, Takashi Yano via Cygwin-apps wrote:
>>> 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?
>>
>> Thanks. I will check the configuration of fedora.
>
> I have checked the configuration of ffmpeg in fedora.
> It seems that most of codecs are disabled in fedora
> by default unless 'all_codecs' flag is specified.
> https://src.fedoraproject.org/rpms/ffmpeg/blob/f37/f/ffmpeg.spec
>
> I have built a ffmpeg package using the configuration
> almost imitated fedora.
> https://tyan0.yr32.net/cygwin/x86_64/release/ffmpeg-free/
>
> You would find this ffmpeg of the above configuration is
> almost unuseful...
> aac, h264, hevc, mpeg4, wma, wmv, etc. are not supported.
>
> I also imitated the configuration with 'all_codecs' flag
> and have built another ffmpeg package.
> https://tyan0.yr32.net/cygwin/x86_64/release/ffmpeg-all_codecs/
>
> This is almost common with the major ports of ffmpeg.
>
> Could you please review them?
Thanks for looking into this. The packaging looks fine from a technical
standpoint.
The concern here is that we have an informal policy to only accept
packages which is would be allowed in Fedora (by it's policies on
content and being free of legal encumbrances (e.g. license, patent and
trademark issues))
After some discussions, it seems that policy should be formal. I've
amended [1] to state that.
I'm sorry to cause you more trouble, but given that, can you package
this based on the codec set in Fedora's ffmpeg-free?
If you don't think the package is useful under those constraints, don't
let this discourage you from offering either the cygport for interested
people to build it themselves, or the packages via an overlay package
server [2]
[1] https://cygwin.com/packaging-contributors-guide.html#submitting
[2] https://cygwin.com/package-server.html#overlay
(Note for the peanut gallery: none of this should be construed as
reflecting my personal opinions on the virtues and validity of software
patents generally, or in this specific case. This is not the place for
discussion of such issues)
next prev parent reply other threads:[~2023-02-04 16:45 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
2023-01-22 12:25 ` Takashi Yano
2023-01-24 3:28 ` Takashi Yano
2023-02-04 16:45 ` Jon Turney [this message]
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=e99baaf9-21a5-ed5c-046d-535a17dd80e9@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).