public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] faad2 (2.8.8)
Date: Mon, 06 Feb 2023 00:10:39 -0500	[thread overview]
Message-ID: <3c43cebe8c2b6159e20a697979bf30910fb359fe.camel@cygwin.com> (raw)
In-Reply-To: <351d817f-b281-6289-b667-f3e51b2e30b1@Shaw.ca>

On Sun, 2023-02-05 at 22:04 -0700, Brian Inglis wrote:
> 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.

Anything blocked from Fedora itself for legal reasons cannot be part of Cygwin
either.  Its inclusion in any other distro or repo is insufficient.

-- 
Yaakov


  reply	other threads:[~2023-02-06  5:10 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
2023-02-06  5:10     ` Yaakov Selkowitz [this message]
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=3c43cebe8c2b6159e20a697979bf30910fb359fe.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --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).