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] speexdsp-1.2rc3-1
Date: Tue, 27 Dec 2016 01:16:00 -0000	[thread overview]
Message-ID: <401881fe-ba62-8cdc-ea96-7b0508e77843@cygwin.com> (raw)
In-Reply-To: <4b277a1d-787d-5af7-483f-55d131782687@acm.org>

On 2016-12-26 18:32, David Rothenberger wrote:
> On 12/26/2016 12:55 PM, Yaakov Selkowitz wrote:
>> This version does not come with the speexdsp library, which is now
>> shipped separately upstream.  This needs to be provided as well in order
>> to not break packages which already use it.  Are you able to ITP speexdsp?
>
> Sure, here you go.

Thanks!  A few nits:

* Why a git snapshot instead of an official tarball?

* A version number of "1.2rc3" may not sort properly with a future 
1.2.0.  Instead, drop all the git stuff and:

VERSION=1.2
RELEASE=0.1.rc3

SRC_URI="http://downloads.xiph.org/releases/speex/speexdsp-${VERSION}${RELEASE##*.}.tar.gz"
SRC_DIR="speexdsp-${VERSION}${RELEASE##*.}"

* The following is problematic:

libspeexdsp1_CONTENTS="usr/bin/*.dll"

NEVER DO THIS.  If the DLL ABI version number is changed upstream 
(either on purpose or by accident), you might miss it and end up 
packaging what should be libspeexdsp2 as libspeexdsp1, breaking existing 
installations.

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.

-- 
Yaakov

  reply	other threads:[~2016-12-27  1:16 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 [this message]
2016-12-27  2:49       ` David Rothenberger
2016-12-27  3:35         ` Yaakov Selkowitz
2016-12-27 19:08           ` David Rothenberger
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=401881fe-ba62-8cdc-ea96-7b0508e77843@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).