From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Cc: Yaakov Selkowitz <yselkowitz@cygwin.com>
Subject: Re: [ITP] faad2 (2.8.8)
Date: Sun, 5 Feb 2023 22:04:04 -0700 [thread overview]
Message-ID: <351d817f-b281-6289-b667-f3e51b2e30b1@Shaw.ca> (raw)
In-Reply-To: <665c5d9796b8f612b860016f52f818de7e7cccb7.camel@cygwin.com>
On 2023-02-05 19:46, Yaakov Selkowitz via Cygwin-apps wrote:
> On Fri, 2023-01-20 at 19:36 +0900, Takashi Yano via Cygwin-apps wrote:
>> I would like to propose a new package FAAD2 which is
>> a decoder library for AAC audio codec. This package
>> is needed by the new package moc I have proposed at
>> the same time. I have already prepared the package at:
>>
>> https://tyan0.yr32.net/cygwin/x86_64/release/faad2/
>
> Unfortunately, this cannot be included in the Cygwin distribution.
These packages are now GPL and available from Arch, Debian main repo, *BSD
ports, OpenSuSE, Slack, and more, so there may have been issues with
non-relocatable non-PIC assembler code, patents now expired/lapsed/challenged,
VideoLan or alternative commercial licensing, for example no commercial use
restrictions?
Many codecs like these can be installed on Fedora, etc. from RPMfusion,
UnitedRPMs, or other repos.
See e.g.
https://repology.org/project/faad2/versions
https://metadata.ftp-master.debian.org/changelogs//main/f/faad2/faad2_2.10.1-1_copyright
--
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-02-06 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 10:36 Takashi Yano
2023-02-06 2:46 ` Yaakov Selkowitz
2023-02-06 5:04 ` Brian Inglis [this message]
2023-02-06 5:10 ` Yaakov Selkowitz
2023-02-06 12:22 ` 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=351d817f-b281-6289-b667-f3e51b2e30b1@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-apps@cygwin.com \
--cc=yselkowitz@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).