From: David Rothenberger <daveroth@acm.org>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] speexdsp-1.2rc3-1
Date: Tue, 27 Dec 2016 19:08:00 -0000 [thread overview]
Message-ID: <349ef0e5-2e80-5fcd-648f-46589250f3f5@acm.org> (raw)
In-Reply-To: <9c345671-4d53-7a25-50e1-7e36de579f67@cygwin.com>
On 12/26/2016 7:35 PM, Yaakov Selkowitz wrote:
> On 2016-12-26 20:49, David Rothenberger wrote:
>> On 12/26/2016 5:16 PM, Yaakov Selkowitz wrote:
>>> * Why a git snapshot instead of an official tarball?
>>
>> I had problems building the latest speex release from the official
>> tarball, so I switched to git for that release and just copied it for
>> speexdsp.
>
> How so? I didn't have any issues building the mingw speex packages.
It wouldn't build the man pages using the official source tarball.
>>> I have added this package under your name. Go ahead and upload with
>>> these fixes, and then I'll fix the dependencies of other packages
>>> accordingly.
>>
>> Done. Thanks for the review and fixing up the dependencies.
>
> One more thing: now that we have speexdsp (again), speexenc (from the
> main speex package) will benefit from it if present. This would require
> a simple revision bump and rebuild of speex with the speexdsp packages
> installed.
Thanks for the heads up. Working on that now.
--
David Rothenberger ---- daveroth@acm.org
"There is nothing new under the sun, but there are lots of old things
we don't know yet."
-- Ambrose Bierce
next prev parent reply other threads:[~2016-12-27 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.53567499-4e31-ae21-e16a-ff3041d8a78d@acm.org>
2016-12-26 20:55 ` Updated: speex-1.2.0-1 Yaakov Selkowitz
2016-12-27 0:33 ` [ITP] speexdsp-1.2rc3-1 David Rothenberger
2016-12-27 1:16 ` Yaakov Selkowitz
2016-12-27 2:49 ` David Rothenberger
2016-12-27 3:35 ` Yaakov Selkowitz
2016-12-27 19:08 ` David Rothenberger [this message]
2016-12-28 3:23 ` Yaakov Selkowitz
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=349ef0e5-2e80-5fcd-648f-46589250f3f5@acm.org \
--to=daveroth@acm.org \
--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).