public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
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: List [ITP],[ITA] by me
Date: Sun, 5 Feb 2023 16:33:45 +0000	[thread overview]
Message-ID: <df238abc-67fe-6bbc-6a0b-6b4591741722@dronecode.org.uk> (raw)
In-Reply-To: <20230205174024.3fd85a3c1dfb33e0c34aafa5@nifty.ne.jp>

On 05/02/2023 08:40, Takashi Yano via Cygwin-apps wrote:
> The list of ITPs and ITAs I recently proposed, is as follows.
> Sorry, there are so many, but thank you in advance.

No problem.  I'll try to give them all the attention they deserve.

> [ITP]
> AMF: for ffmpeg (new)
> aom: for ffmpeg (new)
> faad2 : for moc
> fdk-aac-free : for ffmpeg (new)
> ffmpeg : for moc (under discussion)
> libopusenc : for opus-tools
> mfx_dispatch : for ffmpeg (new)
> moc
> nv-codec-headers : for ffmpeg (new)

I have a question about how this (and AMF I guess) works.

Are these headers which implement the whole codec? or do they expect the 
codec to be accessible via the driver somehow?

> openh264 : for ffmpeg (new)
> xvidcore : for ffmpeg
> 
> [ITA]
> libsndfile : maintainer changed, no GTG yet
> opus : maintainer changed, no GTG yet
> opusfile : maintainer changed, no GTG yet
> opus-tools : maintainer changed, no GTG yet
> pulseaudio : (new)
> 
> SDL2 : already has GTG
> mpg123 : already has GTG
> 
> [WITHDRAW]
> x264
> x265
> 

I've posted some specific comments on some of these.

Please double-check that packages which contain a soversioned library 
include that in the package name (for reasons touched on in [1]).

If you'd like me to review any of these again, please post the just new 
.cygport file in a follow-up (since that will save me a little time in 
having to extract it)

I've updated the package list.

[1] https://cygwin.com/pipermail/cygwin-apps/2023-January/042480.html


  reply	other threads:[~2023-02-05 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05  8:40 Takashi Yano
2023-02-05 16:33 ` Jon Turney [this message]
2023-02-06 12:21   ` Takashi Yano
2023-02-13 18:02     ` Jon Turney
2023-02-14  9:11       ` Takashi Yano
2023-02-14 13:33         ` Takashi Yano
2023-02-16 18:52           ` Jon Turney
2023-02-13 10:47   ` Status update (Re: List [ITP],[ITA] by me) Takashi Yano
2023-02-13 18:29     ` Jon Turney
2023-02-14  9:11       ` Takashi Yano

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=df238abc-67fe-6bbc-6a0b-6b4591741722@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).