From: Peter Ross <pross@xvid.org>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] libmicrohttpd 0.9.52
Date: Wed, 01 Feb 2017 09:07:00 -0000 [thread overview]
Message-ID: <20170201090739.36zxmmctcmzq4med@7c616c24653cac4f1c247e3ee013d12b> (raw)
In-Reply-To: <bd452027-d2bd-5974-3df4-703cde71244f@cygwin.com>
[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]
On Tue, Jan 31, 2017 at 02:03:35PM -0600, Yaakov Selkowitz wrote:
> On 2017-01-31 02:56, Corinna Vinschen wrote:
> > On Jan 30 20:53, Peter Ross wrote:
> > > On Tue, Dec 13, 2016 at 08:25:32PM +1100, Peter Ross wrote:
> > > > Small C library for embedding HTTP server into applications.
> > > > This is not to be confused with the existing 'micro-httpd' cygwin package.
> > > >
> > > > Homepage: https://www.gnu.org/software/libmicrohttpd/
> > > >
> > > > License: LGPL version 2.1
> > > >
> > > > Yep, is packaged by other distro:
> > > > https://packages.debian.org/search?keywords=microhttpd&searchon=names
> > > > https://packages.ubuntu.com/search?keywords=microhttpd&searchon=names
> > > > https://software.opensuse.org/package/libmicrohttpd
> > > > https://admin.fedoraproject.org/pkgdb/package/rpms/libmicrohttpd/
> > > >
> > > > Packages:
> > > > http://pross.sdf.org/sandpit/libmicrohttpd/x86/libmicrohttpd-0.9.52-1.hint
> > > > http://pross.sdf.org/sandpit/libmicrohttpd/x86/libmicrohttpd-0.9.52-1.tar.xz
> > > > http://pross.sdf.org/sandpit/libmicrohttpd/x86/libmicrohttpd-0.9.52-1-src.tar.xz
> > > > http://pross.sdf.org/sandpit/libmicrohttpd/x86_64/libmicrohttpd-0.9.52-1.hint
> > > > http://pross.sdf.org/sandpit/libmicrohttpd/x86_64/libmicrohttpd-0.9.52-1.tar.xz
> > > > http://pross.sdf.org/sandpit/libmicrohttpd/x86_64/libmicrohttpd-0.9.52-1-src.tar.xz
> > > >
> > > > Cygport file:
> > > > [...]
> >
> > Packaging looks good to me.
>
> If this is a library, then there needs to be separate runtime and -devel
> packages.
Thanks, acknowledged.
Further question: this library is currently has soversion 12 and provides cygmicrohttpd-12.dll.
Should the package name also include the so version number, e.g. libmicrohttpd12(-devel)?
If not, what happens when so version changes in future.
Cheers,
-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2017-02-01 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 9:25 Peter Ross
2017-01-30 9:53 ` Peter Ross
2017-01-31 8:56 ` Corinna Vinschen
2017-01-31 20:03 ` Yaakov Selkowitz
2017-02-01 9:07 ` Peter Ross [this message]
2017-02-01 14:43 ` Yaakov Selkowitz
2017-02-01 9:18 ` Corinna Vinschen
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=20170201090739.36zxmmctcmzq4med@7c616c24653cac4f1c247e3ee013d12b \
--to=pross@xvid.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).