From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [WITHDRAW] Re: [ITP] x265 (3.5)
Date: Sun, 5 Feb 2023 10:19:53 -0700 [thread overview]
Message-ID: <06cb56ff-d751-6e8a-31f4-b4a6999058ea@Shaw.ca> (raw)
In-Reply-To: <20230205173954.a0f7a110a227c219f011ad5b@nifty.ne.jp>
On 2023-02-05 01:39, Takashi Yano via Cygwin-apps wrote:
> On Fri, 20 Jan 2023 19:35:47 +0900
> Takashi Yano wrote:
>> I would like to propose new package x265, which is
>> a H265 video codec library. This is needed by ffmpeg
>> package I have proposed at the same time. I guess
>> this package will not used by other packages than
>> ffmpeg, so only the static library is provided by
>> this package.
>>
>> I already prepared the package at the following
>> location.
>>
>> https://tyan0.yr32.net/cygwin/x86_64/release/x265/
>
> I would like to withdraw this ITP because it does not
> seem to align cygwin package policy. This package is
> not ported for fedora due to some reasons.
> https://cygwin.com/packaging-contributors-guide.html#submitting
These packages are now GPL and available from Debian main repo, *BSD ports,
OpenSuSE, and Slack, so maybe there used to be issues with non-relocatable
non-PIC assembler code, patents that expired/lapsed, VideoLan, or alternative
commercial licensing, for example no commercial use restrictions?
Many codecs like these can be installed on Fedora, etc. from RPMfusion repos.
--
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
prev parent reply other threads:[~2023-02-05 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 10:35 Takashi Yano
2023-02-05 8:39 ` [WITHDRAW] " Takashi Yano
2023-02-05 17:19 ` Brian Inglis [this message]
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=06cb56ff-d751-6e8a-31f4-b4a6999058ea@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).