public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: [GOLDSTAR] Re: [ITA] libsndfile (1.2.0)
Date: Sat, 21 Jan 2023 15:02:52 +0000	[thread overview]
Message-ID: <4d337edf-41ee-a41e-596e-59985af6bd52@dronecode.org.uk> (raw)
In-Reply-To: <66963fe9-d09d-da73-e370-6ae1166fa50d@dronecode.org.uk>

On 21/01/2023 14:59, Jon Turney via Cygwin-apps wrote:
> On 21/01/2023 00:20, Takashi Yano via Cygwin-apps wrote:
>> On Fri, 20 Jan 2023 16:40:18 -0700
>> Brian Inglis wrote:
>>> On 2023-01-20 16:22, Takashi Yano via Cygwin-apps wrote:
>>>> Do you mean, keep libsndfile1 and delete libsndfile,
>>>> or vice versa?
>>>
>>> Presumably means to remove libsndfile from PKG_NAMES as it is no 
>>> longer required
>>> by packaging tools and add:
>>>
>>>     libsndfile1_OBSOLETES=libsndfile # no longer required by 
>>> packaging tools
>>>
>>> in libsndfile1 package stanza lines in libsndfile.cygport.
>>
>> Thanks for the advice!
> 
> This is correct.
> 
>> I have updated the package in:
>> https://tyan0.yr32.net/cygwin/x86_64/release/libsndfile/
> 
> Thanks.
> 
> I've given you the adopted packages: libsndfile, mpg123, opus, 
> opus-tools, opusfile, SDL2.  I'll look at the rest later.

Please accept these literally priceless gold stars for adopting these 
packages.


  reply	other threads:[~2023-01-21 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 10:34 Takashi Yano
2023-01-20 15:00 ` Thomas Wolff
2023-01-20 15:20   ` Takashi Yano
2023-01-20 18:21     ` Jon Turney
2023-01-20 23:22       ` Takashi Yano
2023-01-20 23:40         ` Brian Inglis
2023-01-21  0:20           ` Takashi Yano
2023-01-21 14:59             ` Jon Turney
2023-01-21 15:02               ` Jon Turney [this message]
2023-01-27 21:46                 ` [GOLDSTAR] " Andrew Schulman
2023-01-22 12:15               ` Takashi Yano
2023-02-13 10:40                 ` 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=4d337edf-41ee-a41e-596e-59985af6bd52@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).