public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Daisuke Fujimura <booleanlabel@gmail.com>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] libhtp 0.5.42
Date: Tue, 4 Apr 2023 19:25:25 +0100	[thread overview]
Message-ID: <83d19f47-a2c5-a9a0-a192-7efec965861c@dronecode.org.uk> (raw)
In-Reply-To: <CAA3frXRuJ6-1sG2N+xs+7Fp53YoP7Qpitc1V9n+uwpQQxiONSw@mail.gmail.com>

On 02/04/2023 15:17, Daisuke Fujimura via Cygwin-apps wrote:
> Hello,
> 
> [ITP] A new package proposal: libhtp
> 
> - libhtp2
> - libhtp-devel

Thanks!

> 
> ====
> 
> SUMMARY: Security-aware parser for the HTTP protocol
> HOMEPAGE: https://github.com/OISF/libhtp
> SRC_URI: https://github.com/OISF/libhtp/archive/refs/tags/0.5.42.tar.gz
> LICENSE: BSD-3-Clause
> 
> ====
> 
> Corresponding Linux/Unix packages are searched:
> - https://repology.org/project/libhtp/versions
> 
> Cygportfile:
> - https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=shortlog;h=refs/heads/libhtp

You might want to consider writing something like:

libhtp2_CONTENTS="
          usr/bin/*-2.dll
          usr/share
"

So that if and when the soversion changes, packaging fails, rather than 
silently ploughing on to create a libhtp2 package containing 
cyghtp-3.dll, with hilarious consequences.

> 
> Packages, logs:
> - https://github.com/cygwin/scallywag/actions/runs/4587137631 >

Otherwise, looks good.

I added this to your packages.


  reply	other threads:[~2023-04-04 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02 14:17 Daisuke Fujimura
2023-04-04 18:25 ` Jon Turney [this message]
2023-04-06 13:46   ` Daisuke Fujimura

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=83d19f47-a2c5-a9a0-a192-7efec965861c@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=booleanlabel@gmail.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).